Running it
Telegram bot not responding? Work through these in order
By the Botable team
A silent Telegram bot almost always has one of six causes: the process is not running, a webhook conflict, privacy mode in a group, a missing admin permission, a crashed handler, or rate limiting. Check them in that order, it is roughly the order of probability.
Watch it
Where a running bot's output and crashes surface, how to read the traceback that comes with one, and the auto-fix path that hands the error back to the agent.
Read the transcript
Everything said in the video, in order.
A deployed bot is a program running on a machine you will never see. The only honest account of what it is doing is what it writes down while it runs.
That is the Logs tab. It is also where the platform notices a bot has broken, and starts repairing it before you have read a word.
The workspace opens on Manage, and a red number appears on the Logs tab by itself. You are told something is wrong rather than having to go looking.
That number is distinct problems parsed out of the log, not a count of red lines. It disappears once you are on the tab and looking at them.
This is your bot's own output as it runs — every update it handled, every payment it recorded. The figure beside the title is how many lines are being held.
The connection is opened once and kept open, so lines land as the bot writes them. There is no refresh control because there is nothing to refresh.
Colour comes from what the line says. Errors, failures and exceptions go red, warnings amber, starting and running green.
Detection reads only the lines written since the last reload, so a problem you already fixed cannot climb back onto the badge.
Redeploy restarts the bot from the files it has right now. Nothing is rebuilt and nothing is regenerated — the code on disk is the source of truth.
Press it and the panel empties, because the runner wipes that bot's log database as it reloads. What fills it again is only this version starting up.
When a bot's code fails to load, the runner reports it to the platform and a repair starts unprompted. It lands in the chat, labelled Auto-fix.
The agent is given the error, the stack trace and the last fifty lines of log, and told to make the smallest change that fixes it, then read the logs to confirm.
Botable started that run, not you, so it costs no credit. It is kept as its own version, which means you can roll it back like anything else.
You can also ask in the chat. The agent reads the same logs and error records you are reading, so the answer comes from evidence.
Watch the stream, trust the colours, let the platform take the crashes. Start free at botable dot I O.
The short version
A Telegram bot that has stopped responding is rarely a mystery, because the failure surface is small and the causes have a stable order of probability. Most often the process simply is not running, it crashed, the host restarted, or a deploy failed and nobody noticed, since a dead bot produces no error anywhere a user can see. Next most common is a webhook conflict: setting a webhook disables long polling, and running both leaves the bot appearing to receive nothing. In groups, privacy mode explains a bot that answers commands but ignores conversation, while a missing admin permission explains one whose moderation commands silently do nothing. Further down are a handler throwing on a specific input, so the bot answers everything except one thing, and rate limiting, which makes it slow rather than silent. Checking in that order resolves most cases in minutes.
Step by step
Is the process actually running?
Check first, always. A crashed or un-deployed bot is the single most common cause and it is invisible from Telegram, the bot still appears in your chat list and still shows a profile. Look at your logs or your platform's status rather than at the chat.
Is there a webhook conflict?
A bot can use a webhook or long polling, not both. Setting a webhook silently disables getUpdates, so a bot that was polling stops receiving anything the moment a webhook is registered, often by a second deployment or an old test script. Check what the webhook is currently set to and clear it if you intend to poll.
Does it answer commands but ignore everything else in a group?
That is privacy mode, on by default, and it is a setting rather than a fault. Disable it in @BotFather with /setprivacy, then remove the bot from the group and add it back, the change does not apply to groups it is already in.
Do moderation actions do nothing at all?
Missing admin permissions. Deleting messages, restricting and banning each need the bot promoted with that specific right, and Telegram rejects the action silently rather than returning something visible. Open the group's administrator list and read what the bot actually has.
Does it answer some things and not others?
A handler is throwing on a specific input, which takes down that path and leaves the rest working. Reproduce with the exact message that fails and read the log for that request, this pattern is almost never infrastructure and almost always one unhandled case.
Is it slow rather than silent?
Rate limiting. Telegram applies documented soft limits per chat and overall, and a bot that bursts past them is throttled rather than blocked, so messages arrive late in an order that looks random. Batch and space your sends.
What catches people out
- A dead bot looks identical to a working one from the chat list, never diagnose from Telegram alone
- Setting a webhook disables polling silently; this catches people who deploy twice
- Permission failures are silent by design, so "nothing happened" is a permissions symptom, not a null result
Questions
The bot works in private chat but not in the group. Why?
Privacy mode if it ignores conversation, missing admin rights if its actions fail. Those two account for almost every private-works-group-does-not report, and both are settings rather than code problems.
It worked yesterday and stopped overnight. What changed?
Usually the host restarted and the process did not come back, or a token was revoked or rotated. Check the process first and the token second, both fail exactly this way, and neither surfaces an error to the user.
Want a bot that does this?
Describe it in plain language and Botable writes the code, gives the bot its own database, deploys it and keeps it running. Everything on this page is handled for you, the token, the webhook, the storage, the hosting.
Keep reading
- Group privacy modetelegram bot privacy mode
- Webhooks vs pollingtelegram webhook vs polling
- Rate limitstelegram bot rate limits