Message delete not found · message.delete_not_found

Stable ID: message.delete_not_found · Evidence: observed

The message to delete could not be resolved.

The response does not distinguish a deleted message from an incorrect identifier, missing access or a masked lookup error. Batch deletion can skip missing messages; this response is not an inventory of deleted items.

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 delete not found

See matching rules for parameter precedence and unknown or ambiguous results.

Illustrative methods: deleteMessage, deleteMessages.

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

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.

Facts

This condition adds no extracted facts; result.facts is empty.

Example

Synthetic examples derived from the cited source.

API method: deleteMessage.

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

Python

from errorgram import classify

response = {
    "ok": False,
    "error_code": 400,
    "description": "Bad Request: message to delete not found",
}
result = classify(response, method='deleteMessage')

assert result.id == 'message.delete_not_found'
print(result.entry["summary"])

JavaScript and TypeScript

import { classify } from "errorgram";

const response = {
  "ok": false,
  "error_code": 400,
  "description": "Bad Request: message to delete not found"
};
const result = classify(response, { method: "deleteMessage" });

if (result.status === "matched" && result.id === "message.delete_not_found") {
  console.log(result.entry.summary);
}

Framework names

Integration	Type or ID
Python	errorgram.MessageDeleteNotFound
aiogram	errorgram.aiogram.MessageDeleteNotFound extends TelegramBadRequest
grammY	EnrichedGrammyError with classification.id equal to message.delete_not_found

Enrichment is explicit and keeps framework catch compatibility. Follow the Python and aiogram guide or JavaScript, TypeScript, and grammY guide.

Evidence

• Recorded observation. Deleting the test bot’s own message again after confirmed deletion returned this description. Accessed 2026-09-16.
• Bot API 10.3 · telegram-bot-api/Client.cpp:14989–15006. Single and batch deletion use “message to delete”; the batch path permits missing items. 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

Catalogue 0.1.0 · schema 1.0.0 · reviewed 2026-09-16.

Markdown · Condition JSON · Full catalogue and sources · JSON Schema