GuidesChannels

Telegram 409 "Conflict: terminated by other getUpdates request"

Telegram's 409 Conflict means two programs read one bot token, often OpenClaw left running after a move to Hermes. How to find the other one and stop it.

November 14, 2026The Everpod team
The short answer

Two programs are asking Telegram for the same bot’s messages. Each getUpdates request cuts off the one before it, so Telegram answers the loser with error 409, “Conflict: terminated by other getUpdates request; make sure that only one bot instance is running.” The usual second reader is an agent you meant to retire: OpenClaw still running after a move to Hermes, or the reverse; a copy on your laptop beside the one on your server; or two services of the same agent. Stop the one you do not want, or give each agent its own bot token from BotFather.

What you see

From a program built on grammY, the library OpenClaw’s Telegram channel uses, it reads like this in a log:

GrammyError: Call to 'getUpdates' failed! (409: Conflict: terminated by other getUpdates request; make sure that only one bot instance is running)
Copied

Hermes Agent logs the shorter terminated by other getUpdates request, and may retry in a loop. Both are the same refusal from Telegram. The bot does not go fully silent: each reader gets some of the messages while the other is cut off, so a reply comes from whichever program happened to be asking, and the agent you are watching seems to miss messages at random. Nothing is wrong with the token or the network. The message itself says what Telegram wants: one reader per bot. Telegram’s Bot API gives a bot two “mutually exclusive ways of receiving updates”, polling with getUpdates or a webhook, and an agent connected to Telegram polls by default (OpenClaw’s Telegram docs: “Long polling is the default transport”).

OpenClaw and Hermes on one bot

This is the commonest case after a switch. Hermes’s importer brings OpenClaw’s bot token across (it lands as TELEGRAM_BOT_TOKEN when you pass --migrate-secrets, per Nous’s migration guide), and neither hermes claw migrate nor OpenClaw’s own importer is documented as stopping the agent you are leaving. Start the new gateway and you have two readers. The comparison of OpenClaw and Hermes says to run them side by side, if you want to, only on separate chat accounts; this error is what happens when they share one.

Leaving OpenClaw for Hermes, check and stop OpenClaw’s gateway:

openclaw gateway status
openclaw gateway stop
Copied

A plain stop does not survive a reboot. On a Mac, openclaw gateway stop --disable keeps it down; on Linux, openclaw gateway uninstall removes the service without touching the agent’s files, as restarting and stopping OpenClaw explains. Once Hermes has been working for a while, Nous’s hermes claw cleanup renames the leftover OpenClaw folders, and its CLI reference is plain about the effect: “OpenClaw stops working after this.”

Going the other way, stop and remove Hermes’s service:

hermes gateway stop
hermes gateway uninstall
Copied

If you keep several Hermes profiles, hermes gateway stop --all acts on “every profile’s gateway, not just the active” one.

A copy on the laptop and a copy on the server

Moving an agent to a server usually starts on a laptop, and the laptop’s copy keeps running whenever the laptop is awake. So the error can come and go with when the laptop is open. One Hermes report of November 2026 that set out to fix a 409 loop in the code ended with its author finding “a second Hermes gateway on a Mac laptop” on the same token; the patch did nothing while it ran. Run the status command on every computer that has ever had the agent, stop the one you are not keeping, and switch off whatever would start it again, a login item or LaunchAgent on a Mac. The same goes for an old server you moved away from; the steps for moving OpenClaw to a new computer end with keeping the old Gateway stopped for this reason.

Two services of the same agent

Hermes can run its gateway as a systemd user service or as a system service, and it is possible to end up with both, each polling the bot. Nous’s messaging page says to “avoid keeping both the user and system gateway units installed at once unless you really mean to.” Check each:

hermes gateway status
sudo hermes gateway status --system
Copied

Then remove the one you do not want with hermes gateway uninstall or sudo hermes gateway uninstall --system; the Hermes install guide covers which of the two suits a server. For OpenClaw, openclaw gateway status --deep adds a system-wide scan that can report “Other gateway-like services detected (best effort)” with hints for removing stale ones, and OpenClaw’s gateway docs set the expectation: “Most installs should run one gateway per machine.”

Containers

Two container cases produce it. The first is an old container left running beside a new one, after a rebuild under a different name or a second docker run. docker ps lists what is running (Docker’s reference: it “only shows running containers by default”); stop the one you are not using. The second is particular to Hermes in a container whose home folder is shared with the host, as with podman or distrobox. Nous’s messaging page describes it: a user service written there lands in the host’s ~/.config/systemd/user, and “the host’s own systemd --user enables and starts the same unit — a second gateway polling the same bot token.” Current Hermes refuses to install a user service inside a container for this reason. The documented setup is hermes gateway run as the container’s main process, with a restart policy; if an older install left the unit on the host, remove it there.

Something other than an agent

Any program holding the token counts: a notification script, a test bot you ran once, another tool’s Telegram plugin. Claude Code’s Telegram plugin, for one, was reported in March 2026 to leave its old polling process running after a session restart, so the new one met this error; the cause there, in the reporter’s words, was that “Telegram’s Bot API only allows one getUpdates consumer per token.” If you have pasted the token into anything besides your agent, that program is a candidate.

A webhook set on the bot

If something once registered a webhook for the bot, Telegram sends updates there instead, and getUpdates “will not work if an outgoing webhook is set up.” Ask Telegram directly, with your token in place of <token>:

curl https://api.telegram.org/bot<token>/getWebhookInfo
Copied

An empty url in the answer means no webhook: per the Bot API, “If the bot is using getUpdates, will return an object with the url field empty.” A URL there means some program set one. deleteWebhook is the documented way to “switch back to getUpdates”, but if a live service still owns that webhook, it is your second reader and will likely set it again; stop it first. OpenClaw already clears a webhook when it starts polling, and its Telegram troubleshooting page notes that if that call fails on a passing network error, “a still-active webhook then surfaces as a getUpdates conflict”, after which OpenClaw rebuilds its connection. openclaw channels status --probe and openclaw logs --follow show whether it recovered.

When you cannot find the second reader

A forgotten server, a machine you no longer have, or a token that went somewhere it should not: revoke it. Telegram’s bot tutorial notes that each bot’s token “can also be revoked at any time via @BotFather”. In BotFather, send /revoke, pick the bot and put the new token into the one agent you keep, then restart it. Every other copy is left holding a token Telegram no longer accepts, while the bot and its username stay as they were.

Two agents on purpose

If you do want OpenClaw and Hermes both reachable, or a second agent of any kind, give each its own bot: send BotFather /newbot and it will “generate an authentication token for your new bot.” OpenClaw’s own advice for a second gateway is the same, in its multiple-gateways page: “Use a separate Telegram bot token, dedicated to the rescue account.” You then message each agent in its own chat. Connecting the new bot is the same as the first time; the OpenClaw Telegram setup walks through it.

Give your AI agents a permanent cloud computer.

We set it up and secure it, so all you do is use them. Run Claude Code, Codex or any agent you use, more at once than your laptop can hold, and keep them working when it’s closed. Or have OpenClaw set up and run for you.

See the developer pod

From $24/mo · your own plan or API key

Get your OpenClaw agent

$29/mo, cancel anytime · model usage included