Telegram error 400: Bad Request: query is too old and response timeout expired or query ID is invalid

answerCallbackQuery (and the equivalent for inline and shipping/pre-checkout queries) was called with a callback_query_id that Telegram no longer accepts. Every query must be answered within a short window after the user taps; once that passes, or if the ID was already answered, or if it is malformed, Telegram returns this combined description. It does not tell you which of the three applied.

The user experience of this error is a button that shows a loading spinner for a while and then gives up. Your handler probably ran, and may even have edited the message correctly; it just did not acknowledge the tap in time.

This is never a token or permission issue. It is timing or ID reuse.

{"ok":false,"error_code":400,"description":"Bad Request: query is too old and response timeout expired or query ID is invalid"}

Adopt 'acknowledge then act' as a rule for every callback. If a button triggers long work, answer immediately and edit the message when done. Filter replayed updates by message.date so stale callbacks do not reach handlers after an outage.

The companion failure is an edit that no-ops because the content did not change, which surfaces as message is not modified; sloppy handlers often produce both on the same tap. The answer toast itself is capped at 200 characters (see keyboard and callback limits), so long explanations belong in the edited message, not the callback answer.