Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Telegram Long-Polling Handler Hangs Indefinitely on macOS

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Telegram long-polling handler hangs indefinitely on initial getUpdates request and never recovers. Connection timeout configuration is ignored.

Environment

  • OpenClaw: 2026.5.7 (eeef486)
  • OS: macOS 26.4.1 (arm64)
  • Node: 24.15.0
  • Setup: Local gateway (loopback)

Symptoms

  1. Gateway starts and shows [telegram] [default] starting provider (@BotName)
  2. Connection hangs forever on first getUpdates long-poll call
  3. No error messages logged
  4. Timeout configuration (timeout, connectionTimeout, requestTimeout) is ignored
  5. Manual curl tests to Telegram API succeed (bot is valid, token works)
  6. openclaw channels status incorrectly reports "connected" when actually hung
  7. Auto-restart mechanism gives up after 10 attempts

Reproduction

  1. Configure Telegram bot token in openclaw.json
  2. Start gateway: openclaw gateway start
  3. Wait 5+ minutes — Telegram provider never connects

Expected Behavior

  • Connection should either complete and start polling for updates, OR
  • Timeout after configured interval and retry with backoff

Actual Behavior

  • Connection hangs indefinitely
  • No recovery or error messages
  • Status reporting is misleading (shows "connected" when actually hung)

Impact

  • Telegram channel is completely unusable on this setup
  • Affects local gateway deployments on macOS
  • Workaround: Use web UI or webhook mode (not suitable for local-only setups)

Additional Notes

  • Bot token is valid (verified with direct API call)
  • Telegram API is reachable
  • Issue appears to be in gateway's Telegram handler implementation, not the bot or token
  • Affects at least OpenClaw 2026.5.7 (latest stable)
  • Tested with multiple bot tokens and fresh state — same issue persists

Error Message

  1. No error messages logged
  • No recovery or error messages
  • No recovery or error messages

Root Cause

Telegram long-polling handler hangs indefinitely on initial getUpdates request and never recovers. Connection timeout configuration is ignored.

Environment

  • OpenClaw: 2026.5.7 (eeef486)
  • OS: macOS 26.4.1 (arm64)
  • Node: 24.15.0
  • Setup: Local gateway (loopback)

Symptoms

  1. Gateway starts and shows [telegram] [default] starting provider (@BotName)
  2. Connection hangs forever on first getUpdates long-poll call
  3. No error messages logged
  4. Timeout configuration (timeout, connectionTimeout, requestTimeout) is ignored
  5. Manual curl tests to Telegram API succeed (bot is valid, token works)
  6. openclaw channels status incorrectly reports "connected" when actually hung
  7. Auto-restart mechanism gives up after 10 attempts

Reproduction

  1. Configure Telegram bot token in openclaw.json
  2. Start gateway: openclaw gateway start
  3. Wait 5+ minutes — Telegram provider never connects

Expected Behavior

  • Connection should either complete and start polling for updates, OR
  • Timeout after configured interval and retry with backoff

Actual Behavior

  • Connection hangs indefinitely
  • No recovery or error messages
  • Status reporting is misleading (shows "connected" when actually hung)

Impact

  • Telegram channel is completely unusable on this setup
  • Affects local gateway deployments on macOS
  • Workaround: Use web UI or webhook mode (not suitable for local-only setups)

Additional Notes

  • Bot token is valid (verified with direct API call)
  • Telegram API is reachable
  • Issue appears to be in gateway's Telegram handler implementation, not the bot or token
  • Affects at least OpenClaw 2026.5.7 (latest stable)
  • Tested with multiple bot tokens and fresh state — same issue persists

Fix Action

Fix / Workaround

  • Telegram channel is completely unusable on this setup
  • Affects local gateway deployments on macOS
  • Workaround: Use web UI or webhook mode (not suitable for local-only setups)
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

                                                                                                                                                                                                                                                                       Telegram long-polling handler hangs indefinitely on initial getUpdates request and never recovers. Connection timeout configuration is ignored.

Environment

  • OpenClaw: 2026.5.7 (eeef486)
  • OS: macOS 26.4.1 (arm64)
  • Node: 24.15.0
  • Setup: Local gateway (loopback)

Symptoms

  1. Gateway starts and shows [telegram] [default] starting provider (@BotName)
  2. Connection hangs forever on first getUpdates long-poll call
  3. No error messages logged
  4. Timeout configuration (timeout, connectionTimeout, requestTimeout) is ignored
  5. Manual curl tests to Telegram API succeed (bot is valid, token works)
  6. openclaw channels status incorrectly reports "connected" when actually hung
  7. Auto-restart mechanism gives up after 10 attempts

Reproduction

  1. Configure Telegram bot token in openclaw.json
  2. Start gateway: openclaw gateway start
  3. Wait 5+ minutes — Telegram provider never connects

Expected Behavior

  • Connection should either complete and start polling for updates, OR
  • Timeout after configured interval and retry with backoff

Actual Behavior

  • Connection hangs indefinitely
  • No recovery or error messages
  • Status reporting is misleading (shows "connected" when actually hung)

Impact

  • Telegram channel is completely unusable on this setup
  • Affects local gateway deployments on macOS
  • Workaround: Use web UI or webhook mode (not suitable for local-only setups)

Additional Notes

  • Bot token is valid (verified with direct API call)
  • Telegram API is reachable
  • Issue appears to be in gateway's Telegram handler implementation, not the bot or token
  • Affects at least OpenClaw 2026.5.7 (latest stable)
  • Tested with multiple bot tokens and fresh state — same issue persists

Steps to reproduce

Reproduction

  1. Configure Telegram bot token in openclaw.json
  2. Start gateway: openclaw gateway start
  3. Wait 5+ minutes — Telegram provider never connects

Expected behavior

Expected Behavior

  • Connection should either complete and start polling for updates, OR
  • Timeout after configured interval and retry with backoff

Actual behavior

Actual Behavior

  • Connection hangs indefinitely
  • No recovery or error messages
  • Status reporting is misleading (shows "connected" when actually hung)

OpenClaw version

OpenClaw: 2026.5.7 (eeef486)

Operating system

OS: macOS 26.4.1 (arm64)

Install method

No response

Model

na

Provider / routing chain

na

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Expected Behavior

  • Connection should either complete and start polling for updates, OR
  • Timeout after configured interval and retry with backoff
#api#logging issue#authentication issue#prompt issue#agent setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING