openclaw - 💡(How to fix) Fix [Bug]:Discord WebSocket closes (1006) simultaneously with Telegram getUpdates stalls — isolation not working in 2026.5.28

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…

Every ~15-16 minutes, Telegram polling stalls and triggers a restart. At the exact same timestamp, all 3 Discord bots drop with websocket close code 1006. This happens consistently — the timing is not coincidental.

Root Cause

Every ~15-16 minutes, Telegram polling stalls and triggers a restart. At the exact same timestamp, all 3 Discord bots drop with websocket close code 1006. This happens consistently — the timing is not coincidental.

Code Example

- 11:16:29 MDTTelegram stall detected (getUpdates stuck 981s)                                                      
  - 11:16:29 MDT — discord gateway: Gateway websocket closed: 1006 (×3 accounts)                                        
                                                                                                                        
  - 11:23:57 MDTTelegram stall detected (getUpdates stuck 415s)                                                      
  - 11:23:57 MDT — discord gateway: Gateway websocket closed: 1006 (×3 accounts)
RAW_BUFFERClick to expand / collapse

Bug type

Crash (process/app exits or hangs)

Beta release blocker

No

Summary

Every ~15-16 minutes, Telegram polling stalls and triggers a restart. At the exact same timestamp, all 3 Discord bots drop with websocket close code 1006. This happens consistently — the timing is not coincidental.

Steps to reproduce

Outage on multiple applications for communication

Expected behavior

Per the 2026.5.28 release notes, channels should poll independently. Telegram stalls should not affect Discord
connections.

Actual behavior

Discord websockets close (1006) at the precise moment Telegram stall is detected and restarts.

OpenClaw version

2026.5.28

Operating system

macOS 26.5 (arm64)

Install method

npm global

Model

claude sonnet 4.6

Provider / routing chain

openclaw->openrouter->anthropic claude sonnet 4.6

Additional provider/model setup details

Config: 2 Telegram bots, 3 Discord bots, all on the same gateway instance.

Logs, screenshots, and evidence

- 11:16:29 MDT — Telegram stall detected (getUpdates stuck 981s)                                                      
  - 11:16:29 MDT — discord gateway: Gateway websocket closed: 1006 (×3 accounts)                                        
                                                                                                                        
  - 11:23:57 MDT — Telegram stall detected (getUpdates stuck 415s)                                                      
  - 11:23:57 MDT — discord gateway: Gateway websocket closed: 1006 (×3 accounts)

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

Per the 2026.5.28 release notes, channels should poll independently. Telegram stalls should not affect Discord
connections.

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 [Bug]:Discord WebSocket closes (1006) simultaneously with Telegram getUpdates stalls — isolation not working in 2026.5.28