Telegram error 400: Bad Request: message to copy not found
Last verified against Telegram Bot API reference
Bad Request: message to copy not foundWhat error 400 means
copyMessage was asked to copy a message that the bot cannot load from from_chat_id. The description is assembled by the Bot API server from the lookup label "message to copy", so it points at the source message rather than the destination chat or the caption you supplied.
Copying is popular for relaying user messages into an admin or support group, and for re-posting channel content without the "Forwarded from" header. Both patterns depend on the bot having seen the original. If the source is a user's private chat, the user must have started the bot; if it is a channel, the bot must be able to read it. A deleted source message or an ID from another chat fails the same way.
Do not confuse this with the message can't be copied. That one means the message was found but its type (service message, invoice, giveaway, paid media) is not copyable. The batch method copyMessages skips missing IDs instead of failing.
What it looks like
{"ok":false,"error_code":400,"description":"Bad Request: message to copy not found"}Why it happens
- The original message was deleted by the user or an admin before the copy call.
- A relay bot stored the message_id but recorded the destination chat as
from_chat_id. - The bot lost access to the source channel or group after the ID was saved.
- The ID was taken from a different bot token's update stream.
How to fix Telegram error 400
- 1Pass the chat_id from the original update as
from_chat_id, not the chat you are copying to. - 2Confirm the source still exists by attempting the copy immediately after receiving it, not hours later.
- 3Check that the bot is still a member of the source chat via
getChatMemberwith its own user ID. - 4Use
copyMessagesfor bulk relays and compare returned IDs with the requested list.
How to stop it recurring
Relay messages as soon as they arrive instead of queuing raw IDs for later. Keep source and destination as clearly named fields in your queue payload, and alert when relays start failing for one source chat, which usually means the bot was removed there. Membership changes arrive as my_chat_member updates if you subscribe to them.
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?
copyMessage was asked to copy a message that the bot cannot load from from_chat_id . The description is assembled by the Bot API server from the lookup label "message to copy", so it points at the source message rather than the destination chat or the caption you supplied.
How do I fix Telegram error 400?
1. Pass the chat_id from the original update as from_chat_id , not the chat you are copying to. 2. Confirm the source still exists by attempting the copy immediately after receiving it, not hours later. 3. Check that the bot is still a member of the source chat via getChatMember with its own user ID. 4. Use copyMessages for bulk relays and compare returned IDs with the requested list.
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.