Why Are My Telegram Messages Not Being Forwarded?

1. The source chat has not posted anything yet

A rule moves messages that are published after you switch it on. If the source channel has been quiet since then, everything is working exactly as designed and there is nothing to move. This is by far the most common case, and it is worth ruling out first, because from the destination it looks identical to a broken setup.

1. Post a short test message in the source chat yourself.
2. Wait a few seconds, then open the destination.
3. If the test arrives, the rule is healthy and the source was simply quiet.
4. If you also want the messages published before the rule existed, that is a separate operation: a history import.

2. The Telegram login was closed from your phone

When you connect your Telegram account to a forwarding service, Telegram registers a new active login and immediately sends you an alert about it. That alert carries a button that ends the session. Tapping it, or removing the device later from Settings and Devices, revokes the access that reads your chats, and reading stops the moment it is revoked.

This is the most frequent user-side cause we see. The alert looks like a security warning, so people tap the button by reflex, without realising it is the connection they set up themselves a minute earlier.

Clearing it takes one click: open the Telegram page in your dashboard and reconnect. Rules, filters, destinations and settings are untouched and resume immediately. If you ever want to stop the service, disconnect from that same page instead of ending the session from your phone, so the two sides stay in agreement.

3. The destination is refusing the messages

A destination can stop accepting deliveries without anything changing on your side: a write permission was removed, an administrator was demoted, the channel was converted, or the chat was deleted altogether. Telegram then rejects every delivery attempt with a permanent error, and no amount of retrying will change the answer.

When a destination refuses three deliveries in a row for a reason that cannot resolve itself, the rule stops trying and shows you why, next to the rule. That is deliberate: repeating a request that is guaranteed to fail is exactly the behaviour that gets accounts limited, so we protect the account rather than the illusion that the rule is running. Restore the permission in the destination chat, switch the rule back on, and delivery resumes. Your other rules are never affected.

• Check that whoever posts in the destination still has permission to post there.
• Check that the destination channel or group still exists and has not been converted.
• If the destination is a Forum Topic, check that the topic has not been closed or deleted.

4. A filter is dropping everything, silently

Filters do their job without saying anything: a message that does not pass simply never reaches the destination, and no error appears anywhere. It is easy to build a combination that can never match.

• A keyword whitelist forwards only messages containing those words and drops everything else.
• A media type whitelist only applies to messages that carry media: a text-only message is not filtered by it. If your intention was to keep media and drop plain text, that is media-only mode, which is a separate switch.
• Minimum and maximum length quietly remove short posts and long ones.
• A per-user filter on a channel where posts are published by the channel itself can match nothing at all.

1. Open the rule and switch every filter off.
2. Post a test message in the source chat.
3. If it arrives, switch the filters back on one at a time until the one that was blocking shows itself.

5. The rule is pointing at a different chat than you think

Two chats with the same name, a channel that was renamed, a group that was upgraded to a supergroup and changed identifier, or a Forum Topic picked instead of the whole group: in all of these the rule works perfectly and watches something you are not looking at. Open the rule and confirm the exact source and destination, not by their names but by the chats themselves.

6. The source is a protected channel and your plan does not cover it

Channels and groups with "Restrict saving content" enabled are handled from the Smart plan upwards. On the Free plan a rule pointing at a protected source will not deliver, while everything else about that rule looks perfectly healthy, which is what makes this one confusing to diagnose.

7. Telegram has limited the account

Telegram applies its own limits to accounts that send a great deal in a short time, and to accounts that other users report as spam. While a limit is in force, messages to people and chats you have no prior relationship with are refused, and no forwarding service can override that: the restriction lives on the account, not on the rule.

Limits are usually temporary. Slow down, avoid sending in bulk to strangers, and read the dedicated page on why Telegram limits accounts and how to stay under the threshold.

Still nothing? What to send us

If none of the seven applies, contact support with the name of the rule, which destination is affected, roughly when it last delivered, and whether your own test message arrived. With that we can look at the exact delivery attempts for your rule instead of guessing.