openclaw - 💡(How to fix) Fix Regression: Telegram channel Bot API timeouts can starve gateway event loop [1 comments, 2 participants]

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…
GitHub stats
openclaw/openclaw#83961Fetched 2026-05-20 03:45:59
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
1
Timeline (top)
labeled ×2closed ×1commented ×1

After upgrading OpenClaw from 2026.5.7 to 2026.5.18, enabling the Telegram channel caused repeated Telegram Bot API timeouts and gateway event-loop starvation. Disabling Telegram removed these specific timeout logs and improved gateway stability.

This appears to be in the built-in channels/telegram path, not the local telegram-voice-transcriber plugin.

Error Message

2026-05-19T11:52:02.983+09:00 warn fetch-timeout ... elapsedMs=16139 timerDelayMs=6139 eventLoopDelayHint="timer delayed 6139ms, likely event-loop starvation" operation="fetchWithTimeout" url="https://api.telegram.org/.../getMe" 2026-05-19T11:52:21.581+09:00 warn fetch-timeout ... elapsedMs=16399 timerDelayMs=6399 eventLoopDelayHint="timer delayed 6399ms, likely event-loop starvation" operation="fetchWithTimeout" url="https://api.telegram.org/.../getMe" 2026-05-19T11:55:29.032+09:00 warn fetch-timeout ... elapsedMs=15134 timerDelayMs=5134 eventLoopDelayHint="timer delayed 5134ms, likely event-loop starvation" operation="fetchWithTimeout" url="https://api.telegram.org/.../getMe" 2026-05-19T11:55:46.329+09:00 warn fetch-timeout ... elapsedMs=17287 timerDelayMs=7287 eventLoopDelayHint="timer delayed 7287ms, likely event-loop starvation" operation="fetchWithTimeout" url="https://api.telegram.org/.../getMe" 2026-05-19T11:55:46.370+09:00 error channels/telegram telegram deleteMyCommands(all_group_chats) failed: Network request for 'deleteMyCommands' failed!

Root Cause

After upgrading OpenClaw from 2026.5.7 to 2026.5.18, enabling the Telegram channel caused repeated Telegram Bot API timeouts and gateway event-loop starvation. Disabling Telegram removed these specific timeout logs and improved gateway stability.

This appears to be in the built-in channels/telegram path, not the local telegram-voice-transcriber plugin.

Fix Action

Workaround

channels.telegram.enabled=false

After restart, gateway logs showed Telegram was no longer loaded:

http server listening (9 plugins: bonjour, browser, canvas, codex, device-pair, file-transfer, memory-core, phone-control, talk-voice; ...)

Code Example

2026-05-19T11:52:02.983+09:00 warn fetch-timeout ... elapsedMs=16139 timerDelayMs=6139 eventLoopDelayHint="timer delayed 6139ms, likely event-loop starvation" operation="fetchWithTimeout" url="https://api.telegram.org/.../getMe"
2026-05-19T11:52:21.581+09:00 warn fetch-timeout ... elapsedMs=16399 timerDelayMs=6399 eventLoopDelayHint="timer delayed 6399ms, likely event-loop starvation" operation="fetchWithTimeout" url="https://api.telegram.org/.../getMe"
2026-05-19T11:55:29.032+09:00 warn fetch-timeout ... elapsedMs=15134 timerDelayMs=5134 eventLoopDelayHint="timer delayed 5134ms, likely event-loop starvation" operation="fetchWithTimeout" url="https://api.telegram.org/.../getMe"
2026-05-19T11:55:46.329+09:00 warn fetch-timeout ... elapsedMs=17287 timerDelayMs=7287 eventLoopDelayHint="timer delayed 7287ms, likely event-loop starvation" operation="fetchWithTimeout" url="https://api.telegram.org/.../getMe"
2026-05-19T11:55:46.370+09:00 error channels/telegram telegram deleteMyCommands(all_group_chats) failed: Network request for 'deleteMyCommands' failed!

---

channels.telegram.enabled=false

---

http server listening (9 plugins: bonjour, browser, canvas, codex, device-pair, file-transfer, memory-core, phone-control, talk-voice; ...)
RAW_BUFFERClick to expand / collapse

Summary

After upgrading OpenClaw from 2026.5.7 to 2026.5.18, enabling the Telegram channel caused repeated Telegram Bot API timeouts and gateway event-loop starvation. Disabling Telegram removed these specific timeout logs and improved gateway stability.

This appears to be in the built-in channels/telegram path, not the local telegram-voice-transcriber plugin.

Environment

  • OpenClaw: 2026.5.18 (50a2481)
  • macOS: 15.7.4
  • Node: v22.22.0
  • Install path: /usr/local/lib/node_modules/openclaw
  • Telegram was later disabled via channels.telegram.enabled=false

Observed logs

2026-05-19T11:52:02.983+09:00 warn fetch-timeout ... elapsedMs=16139 timerDelayMs=6139 eventLoopDelayHint="timer delayed 6139ms, likely event-loop starvation" operation="fetchWithTimeout" url="https://api.telegram.org/.../getMe"
2026-05-19T11:52:21.581+09:00 warn fetch-timeout ... elapsedMs=16399 timerDelayMs=6399 eventLoopDelayHint="timer delayed 6399ms, likely event-loop starvation" operation="fetchWithTimeout" url="https://api.telegram.org/.../getMe"
2026-05-19T11:55:29.032+09:00 warn fetch-timeout ... elapsedMs=15134 timerDelayMs=5134 eventLoopDelayHint="timer delayed 5134ms, likely event-loop starvation" operation="fetchWithTimeout" url="https://api.telegram.org/.../getMe"
2026-05-19T11:55:46.329+09:00 warn fetch-timeout ... elapsedMs=17287 timerDelayMs=7287 eventLoopDelayHint="timer delayed 7287ms, likely event-loop starvation" operation="fetchWithTimeout" url="https://api.telegram.org/.../getMe"
2026-05-19T11:55:46.370+09:00 error channels/telegram telegram deleteMyCommands(all_group_chats) failed: Network request for 'deleteMyCommands' failed!

Impact

  • Gateway event loop became degraded / starved.
  • Control UI and agent requests became slow or timed out while Telegram was active.
  • Telegram had to be disabled to keep OpenAI/Codex usage stable.

Workaround

channels.telegram.enabled=false

After restart, gateway logs showed Telegram was no longer loaded:

http server listening (9 plugins: bonjour, browser, canvas, codex, device-pair, file-transfer, memory-core, phone-control, talk-voice; ...)

Expected behavior

Telegram polling / command setup should not block or starve the gateway event loop. Bot API timeouts should be isolated so other gateway RPCs and agent runs remain healthy.

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

Telegram polling / command setup should not block or starve the gateway event loop. Bot API timeouts should be isolated so other gateway RPCs and agent runs remain healthy.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Regression: Telegram channel Bot API timeouts can starve gateway event loop [1 comments, 2 participants]