Telegram Bot API · error code

Telegram error 400: Bad Request: message to forward not found

Permanent - do not retryHTTP 400400 Bad Request: identifiers, content and rights

Last verified against Telegram Bot API reference

What Telegram returns
Bad Request: message to forward not found

What error 400 means

forwardMessage could not find the source message identified by from_chat_id and message_id. The destination chat is not the problem here; the Bot API checks the source first and names it in the description ("message to forward").

Bots can only read messages in chats they have access to. Forwarding from a channel requires the bot to be able to read that channel, and forwarding from a private chat requires the user to have talked to the bot. A source message that was deleted, or an ID copied from a different chat, produces the same result. Message IDs are scoped per chat, so 120 in your channel and 120 in your support group are unrelated messages.

The plural method forwardMessages behaves differently: the docs say messages that cannot be found or forwarded are skipped, so a batch call may succeed with fewer IDs returned instead of failing. If you see this error from the single-message method but not from the batch method, that documented skipping behavior is the reason.

What it looks like

{"ok":false,"error_code":400,"description":"Bad Request: message to forward not found"}

Why it happens

  • The source message was deleted from from_chat_id before the forward ran.
  • from_chat_id and message_id came from different chats or different bots' databases.
  • The bot is not a member of the source channel or group and cannot read its history.
  • from_chat_id uses an old basic-group ID after the group was upgraded to a supergroup.

How to fix Telegram error 400

  1. 1Read the message with the same token first (for example by copying it to a log chat) to confirm the bot can see it.
  2. 2Store the source as a (chat_id, message_id) pair taken from the same update object.
  3. 3Add the bot to the source channel or group if it is not a member, then retry.
  4. 4Switch to forwardMessages when partial success is acceptable and inspect which IDs came back.

How to stop it recurring

Capture forward sources at the moment the message arrives and keep them together with the chat they came from. If your workflow forwards older posts, verify access before scheduling. For protected chats, forwarding fails for a different reason; see protected content.

Official reference: Telegram Bot API reference. See all Telegram error codes or the Telegram limits and quotas.

Related codes

Error 400 - quick answers

What does Telegram error 400 mean?

forwardMessage could not find the source message identified by from_chat_id and message_id . The destination chat is not the problem here; the Bot API checks the source first and names it in the description ("message to forward"). Bots can only read messages in chats they have access to.

How do I fix Telegram error 400?

1. Read the message with the same token first (for example by copying it to a log chat) to confirm the bot can see it. 2. Store the source as a (chat_id, message_id) pair taken from the same update object. 3. Add the bot to the source channel or group if it is not a member, then retry. 4. Switch to forwardMessages when partial success is acceptable and inspect which IDs came back.

Should I retry after error 400?

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.