Telegram error 403: Forbidden: the group chat was deleted
Last verified against Telegram Bot API reference
Forbidden: the group chat was deletedWhat error 403 means
The basic group you are addressing is no longer active and was not upgraded to a supergroup. The Bot API server emits this text for a basic group that is inactive and has no supergroup it migrated to, which is the deleted case. Any write action on that chat_id returns it.
There is nothing to fix on the bot side and no new ID to switch to. Compare the upgrade case: when a basic group becomes a supergroup, the old ID also stops working, but that migration error includes migrate_to_chat_id. Without that parameter, the group is gone.
Bots that serve many groups over a long period accumulate these. They are harmless individually but waste requests if a scheduler keeps targeting them, and they can hide real failures in dashboards that count all 403s together. Classify this description separately from blocked and kicked errors so the numbers stay meaningful.
What it looks like
{"ok":false,"error_code":403,"description":"Forbidden: the group chat was deleted"}Why it happens
- The group's creator deleted the group.
- The group became inactive and was not migrated to a supergroup.
- Your database kept the chat long after activity stopped.
How to fix Telegram error 403
- 1Mark the chat as deleted and remove it from all schedules and broadcast lists.
- 2Do not retry; the condition is permanent for that ID.
- 3If the group's members created a replacement, wait for an update from the new chat and store its ID.
How to stop it recurring
Clean up chats that return permanent 403 errors automatically and alert only on unusual spikes. Record the date a chat was last reachable so you can audit removals later. Keeping broadcast lists free of dead chats preserves capacity under the rate limits for chats that still exist.
Official reference: Telegram Bot API reference. See all Telegram error codes or the Telegram limits and quotas.
Related codes
Error 403 - quick answers
What does Telegram error 403 mean?
The basic group you are addressing is no longer active and was not upgraded to a supergroup. The Bot API server emits this text for a basic group that is inactive and has no supergroup it migrated to, which is the deleted case. Any write action on that chat_id returns it. There is nothing to fix on the bot side and no new ID to switch to.
How do I fix Telegram error 403?
1. Mark the chat as deleted and remove it from all schedules and broadcast lists. 2. Do not retry; the condition is permanent for that ID. 3. If the group's members created a replacement, wait for an update from the new chat and store its ID.
Should I retry after error 403?
No. Retrying the same request produces the same error; the condition has to be fixed first. Treat it as a permanent failure for that message and surface it, rather than looping.
Stop debugging Telegram by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.