Telegram "conflict" (409)
Who this is for: an owner whose Telegram bot stopped with a 409.
Telegram lets exactly one program read a bot’s messages. When a second one connects with the same token, Telegram answers 409 Conflict — terminated by other getUpdates request, and the agent’s channel goes into error after a few retries.
Where the second reader usually is
Section titled “Where the second reader usually is”- Another agent in this office with the same token — the app refuses that on save, but an older setup may still have it.
- The same bot on another computer (an old test, a colleague’s machine).
- A previous copy of the app that did not close properly — quit and reopen the app.
- Stop the other reader, or create a new bot with @BotFather and use its token here.
- Open Settings → Accounts, click the agent’s Telegram row, paste the new token, Save.
- Test connection; the badge turns connected.
