Stop Forwarding Loops
Stop copied messages from bouncing between chats by ignoring bot messages or blocking the bot that sends the copies.
A forwarding loop happens when a copied message comes back into a chat that another automation is watching. That automation copies it again, and the messages keep going back and forth—even after people stop posting.
For example, one automation copies Discord → Telegram, while another copies the same Telegram chat → the same Discord channel:
Discord channel → Telegram chat → Discord channel → Telegram chat → …
The bot's copy is being treated as a new message. This can happen between different platforms or between chats on the same platform, with one automation or several.
First, stop the repeated deliveries
Stop the automations involved while you change their settings. You do not need to delete them or rebuild your destinations. Once you have blocked the messages that come back, you can start the automations again.
Option 1: Ignore messages from bots
Use this if you only want to copy messages written by people. It is the simplest choice when you do not need any bot-authored posts.
- Open the automation that reads a chat where the other automation's bot is posting.
- Select that source chat—the place this automation monitors and where the returning copies appear.
- Open Filters → Forward Options.
- Turn Bot Messages off—leave its checkbox unchecked.
- Select Save Changes. Repeat for the other direction where needed.
For example, in the automation copying Telegram → Discord, ignore the Telegram bot that delivers the Discord → Telegram copies. Those copies stay in Telegram, but they are not sent back to Discord.
This also excludes other bot messages from that chat. If you want to keep useful bots, such as alerts or announcements, use Option 2 instead. Forward Options explains this setting.
Option 2: Block only the bot sending the copies
Use a Blocklist to exclude your delivery bot while keeping messages from other bots.
Choose how to identify the bot:
- Author Name: start with the bot's visible name if it stays the same. Use Exact to match the full name.
- @Username: use its username without the
@. This is usually more stable than its visible name, but it can change too. - User ID: the most reliable option if names might change. Select the bot under Block Users, or enter its ID manually. Learn how to find a User ID.
- Open the automation that would copy the delivered message back.
- Click the original chat this automation monitors, where the returning copies appear, then open Filters → Blocklist.
- Add the bot's name or username rule. If you prefer its ID, select it under Block Users. If it is missing, choose Add manually, enter the ID, and press Enter or select +.
- Select Save Changes. Repeat for the delivery bot in the other direction where needed.
Block the bot shown as the sender of the delivered copy, not the person who wrote the original message. See Filters → Block an author for more examples.
When the sender does not appear as a bot
The fix must match how the platform presents the copied message:
- Discord webhooks: copies can display the original person's name and photo. That appearance does not make them human-authored posts; ignoring Bot Messages can still exclude webhook deliveries. For a specific-author Blocklist, use the webhook sender's ID, not the original person's ID.
- Telegram channels: a post can appear as the channel rather than the bot that published it. Bot Messages may not identify it as a bot post. Keep the channel receiving copies out of the chats copied back, or use separate receiving chats for each direction.
- Other senders: if the platform does not identify the sender as a bot, the Bot Messages option is not enough. Block the actual sender where possible, or separate the chats you copy from and deliver to.
Check both directions before leaving it running
Start the automations again, then ask someone to send one new message on each side:
| New message | Expected result |
|---|---|
| A person posts in Discord | One copy appears in Telegram; that copy does not come back |
| A person posts in Telegram | One copy appears in Discord; that copy does not come back |
If copies continue appearing without new posts, stop the automations again and check which sender is being copied back. Check all automations watching those same chats—not just the two you first noticed. Also check that a chat-specific setting is not overriding your choice in Global Settings; How Settings Work explains this.
For repeated messages that do not bounce between chats, see Duplicate messages.