answerCallbackQuery returns 400 "query is too old" immediately after button press — Telegram inline keyboard

Questions
, ,
1

:bullseye: What is your goal?

When a user presses an inline keyboard button in Telegram, I want to answer the callback query (to remove the spinner) and then continue processing the route (update Airtable, send confirmation message).

:thinking: What is the problem & what have you tried?

Module 130 (Telegram Bot → Make an API Call → answerCallbackQuery) always returns [400] Bad Request: query is too old and response timeout expired or query ID is invalid — even when the button is pressed immediately and the scenario runs within 1 second.

The identical configuration in Module 117 (same scenario, same connection, same mapper) works perfectly every time. The only difference is the filter: Module 117 filters for “addsch_” callbacks, Module 130 filters for “pubnow_” callbacks.

:clipboard: Error messages or input/output bundles

Error: [400] Bad Request: query is too old and response timeout expired or query ID is invalid
Code: RuntimeError
Origin: Telegram Bot
Module: 130 (Telegram Bot - Make an API Call - answerCallbackQuery)
Run ID: 16f9ef32f29846fc895702d00ba0bdef
Scenario ID: 5635233 (eu1)

:camera_with_flash: Screenshots (scenario flow, module settings, errors)

Error[400] Bad Request.png
Error[400] Bad Request.png1905×883 233 KB

4

Hello,

Double-check that callback_query_id is mapped dynamically – make sure there are no extra characters and that you’re not using hardcoded data.

Also, keep in mind we’re volunteers here and can’t access your account or scenario directly.
To help you further, please share the blueprint or use the Share Scenario option.

Have a nice day,
Michal