Summary

The Telegram channel plugin sometimes goes silent periodically — it stops responding to or delivering messages until something kicks it back to life (e.g., restarting the TUI or gateway).

Symptoms

• User sends messages via Telegram, but no responses are delivered
• Logs show runs completed successfully (run_completed, aborted=false) with no send errors
• No explicit "message sent to Telegram" log or error during silent periods
• Issue resolves after restarting the TUI or bouncing the gateway

Observed Behavior

From debugging session on 2026-01-25:

• Messages were being processed (visible in logs with ~3-4 second run times)
• Responses appeared in webchat but NOT in Telegram during the silent period
• Relaunching the TUI unblocked Telegram delivery
• After restart, messages appeared in both TUI and Telegram simultaneously

Suspected Causes

1. Session lock — TUI or another client may hold a lock that blocks outbound sends
2. Websocket backpressure — Gateway waiting for acknowledgment before releasing messages to Telegram
3. Event loop stuck — Something in a client connection blocking the main send path
4. Routing state corruption — Multi-client session (webchat + Telegram) causing routing confusion

Reproduction

• Use Telegram and another client (webchat/TUI) on the same session
• After some time, Telegram may stop receiving responses while other clients continue to work
• Workaround: Restart the TUI or gateway to restore Telegram delivery

Environment

• macOS (Apple Silicon)
• Telegram bot with polling mode
• Multiple clients connected to same session (Telegram + webchat/TUI)

Expected Behavior

Telegram should reliably deliver all responses to messages originating from Telegram, regardless of other connected clients or session activity.