Telegram Bot API · error code

Telegram error 400: Bad Request: chat description is not modified

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

Last verified against Telegram Bot API reference

What Telegram returns
Bad Request: chat description is not modified

What error 400 means

setChatDescription was called with the description the chat already has. When nothing would change, Telegram's servers answer with CHAT_ABOUT_NOT_MODIFIED, which the Bot API server turns into the readable sentence above.

Like message is not modified for message edits, it is reported as an error but means nothing needs doing: the chat already shows the text you wanted. The bot has the rights it needs, otherwise the call would have failed on permissions first, and the description is within the documented 0-255 characters.

It usually comes from sync jobs that push the same description on every run, or from deploy scripts that set chat metadata unconditionally. Whitespace differences count as changes, so trimming the stored value consistently matters if you compare before calling. Retries after a network timeout are another source: the first call succeeded, the response was lost, and the repeat finds nothing left to change.

What it looks like

{"ok":false,"error_code":400,"description":"Bad Request: chat description is not modified"}

Why it happens

  • A scheduled job sets the description on every run without checking the current value.
  • Multiple workers apply the same update concurrently and the second one finds nothing to change.
  • A retry after a timeout repeats a change that already succeeded.

How to fix Telegram error 400

  1. 1Read the current value from getChat (the description field) and skip the call if it matches.
  2. 2Treat this description as success in your error handler.
  3. 3Normalize whitespace and line endings before comparing values.

How to stop it recurring

Make metadata updates idempotent: compare with the current value first, and handle the not-modified response as success rather than paging someone. Store the last value you set per chat so you can skip calls without an extra getChat. This also saves requests against the rate limits when a job manages many chats.

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?

setChatDescription was called with the description the chat already has. When nothing would change, Telegram's servers answer with CHAT_ABOUT_NOT_MODIFIED , which the Bot API server turns into the readable sentence above. Like message is not modified for message edits, it is reported as an error but means nothing needs doing: the chat already shows the text you wanted.

How do I fix Telegram error 400?

1. Read the current value from getChat (the description field) and skip the call if it matches. 2. Treat this description as success in your error handler. 3. Normalize whitespace and line endings before comparing values.

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.