openclaw - 💡(How to fix) Fix Telegram polling stalls and sendMessage failures on Windows multi-bot (v2026.4.24–.25) [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#76164Fetched 2026-05-03 04:41:34
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
2
Author
Timeline (top)
closed ×1commented ×1cross-referenced ×1unsubscribed ×1

Split from #75687 (closed prematurely — only Bugs 1–2 were addressed on main). This is Bug 3 from that report.

On Windows with 8 Telegram bots, versions .24 and .25 exhibit Telegram polling stalls and sendMessage failures that make agents appear completely unresponsive.

What happens

After gateway boot, Telegram polling stalls are detected and force-restarted, but recovery fails and agents stop delivering messages:

[telegram] Polling stall detected (active getUpdates stuck for 138.99s); forcing restart.
[telegram] sendMessage failed: Network request for 'sendMessage' failed!

The gateway enters tight restart loops. The first message after boot may occasionally sneak through, then all subsequent messages are lost.

This is distinct from the startup fanout saturation fixed by CHANNEL_STARTUP_CONCURRENCY = 4 on main — the polling stalls occur after successful boot, during normal operation.

Environment

openclaw: v2026.4.24, v2026.4.25 (broken) — v2026.4.23 (working)
node: 22.21.1
os: Windows 11 Pro N (10.0.26200)
platform: win32
bots: 8 Telegram accounts
plugins: acpx, bonjour, browser, device-pair, file-transfer, memory-core, phone-control, talk-voice, telegram
launcher: Pinokio

Root Cause

Split from #75687 (closed prematurely — only Bugs 1–2 were addressed on main). This is Bug 3 from that report.

On Windows with 8 Telegram bots, versions .24 and .25 exhibit Telegram polling stalls and sendMessage failures that make agents appear completely unresponsive.

What happens

After gateway boot, Telegram polling stalls are detected and force-restarted, but recovery fails and agents stop delivering messages:

[telegram] Polling stall detected (active getUpdates stuck for 138.99s); forcing restart.
[telegram] sendMessage failed: Network request for 'sendMessage' failed!

The gateway enters tight restart loops. The first message after boot may occasionally sneak through, then all subsequent messages are lost.

This is distinct from the startup fanout saturation fixed by CHANNEL_STARTUP_CONCURRENCY = 4 on main — the polling stalls occur after successful boot, during normal operation.

Environment

openclaw: v2026.4.24, v2026.4.25 (broken) — v2026.4.23 (working)
node: 22.21.1
os: Windows 11 Pro N (10.0.26200)
platform: win32
bots: 8 Telegram accounts
plugins: acpx, bonjour, browser, device-pair, file-transfer, memory-core, phone-control, talk-voice, telegram
launcher: Pinokio

Fix Action

Fix / Workaround

This is distinct from the startup fanout saturation fixed by CHANNEL_STARTUP_CONCURRENCY = 4 on main — the polling stalls occur after successful boot, during normal operation.

Code Example

[telegram] Polling stall detected (active getUpdates stuck for 138.99s); forcing restart.
[telegram] sendMessage failed: Network request for 'sendMessage' failed!

---

openclaw: v2026.4.24, v2026.4.25 (broken) — v2026.4.23 (working)
node: 22.21.1
os: Windows 11 Pro N (10.0.26200)
platform: win32
bots: 8 Telegram accounts
plugins: acpx, bonjour, browser, device-pair, file-transfer, memory-core, phone-control, talk-voice, telegram
launcher: Pinokio
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Split from #75687 (closed prematurely — only Bugs 1–2 were addressed on main). This is Bug 3 from that report.

On Windows with 8 Telegram bots, versions .24 and .25 exhibit Telegram polling stalls and sendMessage failures that make agents appear completely unresponsive.

What happens

After gateway boot, Telegram polling stalls are detected and force-restarted, but recovery fails and agents stop delivering messages:

[telegram] Polling stall detected (active getUpdates stuck for 138.99s); forcing restart.
[telegram] sendMessage failed: Network request for 'sendMessage' failed!

The gateway enters tight restart loops. The first message after boot may occasionally sneak through, then all subsequent messages are lost.

This is distinct from the startup fanout saturation fixed by CHANNEL_STARTUP_CONCURRENCY = 4 on main — the polling stalls occur after successful boot, during normal operation.

Environment

openclaw: v2026.4.24, v2026.4.25 (broken) — v2026.4.23 (working)
node: 22.21.1
os: Windows 11 Pro N (10.0.26200)
platform: win32
bots: 8 Telegram accounts
plugins: acpx, bonjour, browser, device-pair, file-transfer, memory-core, phone-control, talk-voice, telegram
launcher: Pinokio

Steps to reproduce

  1. Windows 11, Node 22
  2. Configure 8 Telegram bot accounts
  3. Install openclaw v2026.4.24 or v2026.4.25
  4. Start gateway, send messages to any bot
  5. First message may get through; subsequent messages are lost
  6. Logs show polling stall detection and sendMessage failures

Expected behavior

Telegram polling should remain stable after boot. Messages should be delivered reliably to all 8 bots.

Actual behavior

Polling stalls after 60–139s, forced restarts fail to recover, sendMessage calls fail with network errors. Agents appear completely unresponsive. Rolling back to .23 immediately restores functionality.

OpenClaw version

v2026.4.24, v2026.4.25

Operating system

Windows

Related issues

  • Parent: #75687 (closed — only startup fanout and Bonjour crash were fixed)
  • Related: #75707 (broader event loop saturation — still open)

extent analysis

TL;DR

Downgrade to openclaw version v2026.4.23 to resolve the Telegram polling stalls and sendMessage failures.

Guidance

  • Verify that the issue is specific to Windows and openclaw versions v2026.4.24 and v2026.4.25 by testing on other platforms or versions.
  • Check the network configuration and ensure that there are no external factors causing the network request failures for 'sendMessage'.
  • Consider testing with a reduced number of Telegram bot accounts to see if the issue is related to the number of accounts configured.
  • Review the related issues, especially #75707, to see if there are any known event loop saturation problems that could be contributing to the polling stalls.

Example

No code snippet is provided as the issue seems to be related to a specific version of openclaw and not a coding error.

Notes

The issue seems to be specific to openclaw versions v2026.4.24 and v2026.4.25 on Windows, and downgrading to version v2026.4.23 resolves the issue. However, this may not be a long-term solution, and the root cause of the problem should be investigated further.

Recommendation

Apply workaround: Downgrade to openclaw version v2026.4.23, as it has been confirmed to resolve the issue, and the root cause of the problem in versions v2026.4.24 and v2026.4.25 is still unknown.

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 should remain stable after boot. Messages should be delivered reliably to all 8 bots.

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 Telegram polling stalls and sendMessage failures on Windows multi-bot (v2026.4.24–.25) [1 comments, 2 participants]