GuidesChannels

Telegram "message thread not found": why your agent's bot fails

Telegram's 400 "message thread not found" means the agent sent to a topic that isn't there: a deleted topic, General, or the Nov 2026 private-topic fault.

November 19, 2026The Everpod team
The short answer

Your agent asked Telegram to post into a topic, by its message_thread_id, and Telegram has no such topic in that chat. Usually the agent has kept the id of a topic that was deleted, or the id belongs to the General topic, which Telegram refuses as a send target. Start a new message in a topic that exists, or point the scheduled job at one. If the topics are in a private chat with the bot and the failures began on November 9, 2026, often alongside BOT_TOPIC_WRONG_HOME, that was a fault on Telegram’s side, and users report it fixed from about 10:40 UTC on November 10: topics made during the outage stay broken, so make new ones.

What the message means

400 Bad Request: message thread not found
Copied

Topics exist in two places. A group switched to topics is a forum supergroup; and since Bot API 9.3 and 9.4 (December 2025 and February 2026), a bot can have topics in its private chat with a user, created by the user or by the bot itself. In both, the Bot API takes a message_thread_id to say which topic a message goes to, and the id belongs to that chat. This error is Telegram saying the id it was given does not name a topic it can post to there. The bot token, the connection and the model are all fine; only that one destination is wrong, so messages elsewhere still work.

The everyday causes

An id the agent stored for a topic that is gone. Agents remember where to answer. A scheduled job that delivers to a topic keeps that topic’s id, and so does the conversation the agent tied to it. Delete or replace the topic and every later send to it fails. OpenClaw users have met both forms: a daily job that failed every day until someone noticed, and a conversation holding a stale thread id that, as of v2026.10.8, had no supported command to clear (the reporter’s operators edited the session store by hand, which is theirs to choose and not a documented route). For a scheduled job, change its delivery to a topic that exists or to the chat itself; the OpenClaw cron guide covers how jobs deliver. For a conversation, starting a fresh one from inside a live topic gives the agent a current id.

The General topic. A forum’s General topic has thread id 1, and OpenClaw’s docs record that “Telegram rejects sendMessage(...thread_id=1) with ‘thread not found’”, so OpenClaw leaves the id off when it posts to General. Your own bot, or a hand-written target that says topic 1, should do the same: post to the group with no thread id.

An id from somewhere else. A topic id copied from one group into another chat’s config, or a group that was recreated, leaves a number that means nothing in the chat it is sent to. In OpenClaw, per-topic settings live under channels.telegram.groups.<chatId>.topics.<threadId>, so check that each topic id sits under the chat it came from.

The November 2026 private-topic fault

From November 9, 2026, bots could not create topics in private chats: Telegram answered createForumTopic with 400 Bad Request: BOT_TOPIC_WRONG_HOME, an error it does not document, and Hermes Agent users saw replies to new private topics fail with “message thread not found” while older topics kept working, and Hermes’s maintainer wrote that it traced “to a Telegram server-side regression”. The report on Telegram’s Bot API tracker was closed as completed on November 10 without a word from Telegram.

What happened next is what users wrote there, not anything Telegram stated: creating topics worked again from about 10:40 UTC on November 10; topics created during the outage, from about 15:33 UTC on November 9, “stay dead; only new ones work”; and one user found all their earlier topics renamed “x”. So if a private topic made in that window still fails, abandon it and open a new one rather than waiting for it to come back.

What your agent does when it happens

The two agents chose opposite defaults, so the symptom differs. Since May 2026, OpenClaw no longer retries a failed topic send in the main chat; the message fails, so in a group a reply cannot land in the wrong topic or in front of everyone. Hermes, since a change merged on November 9, 2026, sends a reply meant for a dead private topic to the root of the chat and forgets that topic, so you see the answer outside the topic instead of nothing. Either way, the answer is the same: give the agent a topic that exists. If the bot stops replying everywhere, not just in one topic, the cause is elsewhere; a 409 Conflict means two programs are reading one bot token, and the Telegram setup guide walks the connection from the start.

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