Troubleshooting

Common issues and checks

Troubleshooting

Common issues and checks

Troubleshooting (first checks)

What to do when your bot stops working? First, check your button/trigger types. Next, check if changes were saved and read the runtime logs. Only as a last resort should you suspect Telegram or external API issues.

A button press does not trigger the expected flow

• Check button type first: Reply Keyboard vs Inline Keyboard.
• Reply Keyboard -> use Text Trigger. Inline Keyboard -> use Callback Trigger.
• Inspect logs to confirm whether Telegram sent message or callback_query.

Action setVariable worked but value is not visible in System

• System variables list shows configuration variables, not runtime session state.
• Runtime value is usually visible via next Message node ({{var}}) or logs.

Save/Test behaves inconsistently

• Check dev server terminal for auth/rate-limit errors.
• Confirm session refresh/cookies are working normally.
• Restart dev server if auth rate-limit errors accumulate.

Logs are empty or not updating

• Confirm Test mode is active.
• Confirm the bot receives the Telegram event (token/config is valid).
• Restart Test and rely on the logs panel if UI polling is briefly delayed.

Hydration mismatch appears (dates/formatting)

• Use explicit locale and timezone for date formatting.
• Avoid unstable SSR-rendered values unless necessary.