Message forward not found · message.forward_not_found
Stable ID: message.forward_not_found · Evidence: source derived
The message to forward could not be resolved.
The response does not distinguish a deleted message from an incorrect identifier, missing access or a masked lookup error.
When it matches
Section titled “When it matches”Every field in a rule must match. Alternative rules are joined with OR. Codes below are JSON response fields, not inferred HTTP statuses.
- JSON
error_code: 400.
Exact description:
Bad Request: message to forward not foundSee matching rules for parameter precedence and unknown or ambiguous results.
Illustrative methods: forwardMessage, forwardMessages.
Possible causes
Section titled “Possible causes”- The message identifier is missing or nonpositive.
- The bot cannot access messages in the chat.
- A message lookup failed and its original error was replaced.
Before deciding what to do
Section titled “Before deciding what to do”Application decision: inspect message target and access. Repeat request: after relevant change.
- Check the chat and message identifiers together, then confirm the bot can access the target message.
These are application choices. Errorgram does not retry, suppress the error, or change bot state.
This condition adds no extracted facts; result.facts is empty.
Example
Section titled “Example”Synthetic examples derived from the cited source.
API method: forwardMessage.
{ "ok": false, "error_code": 400, "description": "Bad Request: message to forward not found"}Python
Section titled “Python”from errorgram import classify
response = { "ok": False, "error_code": 400, "description": "Bad Request: message to forward not found",}result = classify(response, method='forwardMessage')
assert result.id == 'message.forward_not_found'print(result.entry["summary"])JavaScript and TypeScript
Section titled “JavaScript and TypeScript”import { classify } from "errorgram";
const response = { "ok": false, "error_code": 400, "description": "Bad Request: message to forward not found"};const result = classify(response, { method: "forwardMessage" });
if (result.status === "matched" && result.id === "message.forward_not_found") { console.log(result.entry.summary);}Framework names
Section titled “Framework names”| Integration | Type or ID |
|---|---|
| Python | errorgram.MessageForwardNotFound |
| aiogram | errorgram.aiogram.MessageForwardNotFound extends TelegramBadRequest |
| grammY | EnrichedGrammyError with classification.id equal to message.forward_not_found |
Enrichment is explicit and keeps framework catch compatibility. Follow the Python and aiogram guide or JavaScript, TypeScript, and grammY guide.
Evidence
Section titled “Evidence”- Bot API 10.3 · telegram-bot-api/Client.cpp:14441–14452. The forwardMessage path checks the source as “message to forward”. Revision
e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1. - Bot API 10.3 · telegram-bot-api/Client.cpp:9084–9102. Missing identifiers and unavailable message access produce this operation-specific fallback. Revision
e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1. - Bot API 10.3 · telegram-bot-api/Client.cpp:7390–7399. Failed lookups use the same fallback when an empty result is not allowed. Revision
e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1. - Bot API 10.3 · telegram-bot-api/Client.cpp:85–108. The fallback replaces only errors normalized to code 400. Revision
e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1. - Bot API 10.3 · telegram-bot-api/Client.cpp:165–205. Adds the code-specific prefix and lowercases only the initial character of ordinary messages. Revision
e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1.
Source references identify the reviewed revision, not the first release that introduced this response.
Data and versions
Section titled “Data and versions”Catalogue 0.1.0 · schema 1.0.0 · reviewed 2026-09-16.
Markdown · Condition JSON · Full catalogue and sources · JSON Schema