Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Gateway crash-loop on 2026.4.5 — Uncaught exception: Attempted to reconnect zombie connection after disconnecting first (Telegram provider) [2 comments, 3 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#62038•Fetched 2026-04-08 03:09:56
View on GitHub
Comments
2
Participants
3
Timeline
4
Reactions
0
Author
jaspervanveenjaspervanveen
Participants
jaspervanveenjaspervanveenStache73Stache73Vksh07Vksh07
Timeline (top)
commented ×2mentioned ×1subscribed ×1

After upgrading to 2026.4.5, the gateway enters a crash-loop, restarting every ~60 seconds. The Control UI disconnects and reconnects with each restart.

Error Message

The following uncaught exception appears in ~/.openclaw/logs/gateway.err.log on every cycle:

[openclaw] Uncaught exception: Error: Attempted to reconnect zombie connection after disconnecting first (this shouldn't be possible)
    at Object.reconnectCallback (file:///opt/homebrew/lib/node_modules/openclaw/dist/provider-DR2mO1YM.js:13811:26)
    at Timeout.sendHeartbeat [as _onTimeout] (file:///opt/homebrew/lib/node_modules/openclaw/dist/provider-DR2mO1YM.js:13462:12)
    at listOnTimeout (node:internal/timers:605:17)
    at processTimers (node:internal/timers:541:7)

Root Cause

After upgrading to 2026.4.5, the gateway enters a crash-loop, restarting every ~60 seconds. The Control UI disconnects and reconnects with each restart.

Fix Action

Workaround

Rolling back to 2026.4.2 resolves the issue:

npm install -g [email protected]

Code Example

[openclaw] Uncaught exception: Error: Attempted to reconnect zombie connection after disconnecting first (this shouldn't be possible)
    at Object.reconnectCallback (file:///opt/homebrew/lib/node_modules/openclaw/dist/provider-DR2mO1YM.js:13811:26)
    at Timeout.sendHeartbeat [as _onTimeout] (file:///opt/homebrew/lib/node_modules/openclaw/dist/provider-DR2mO1YM.js:13462:12)
    at listOnTimeout (node:internal/timers:605:17)
    at processTimers (node:internal/timers:541:7)

---

npm install -g openclaw@2026.4.2
RAW_BUFFERClick to expand / collapse

Description

After upgrading to 2026.4.5, the gateway enters a crash-loop, restarting every ~60 seconds. The Control UI disconnects and reconnects with each restart.

Error

The following uncaught exception appears in ~/.openclaw/logs/gateway.err.log on every cycle:

[openclaw] Uncaught exception: Error: Attempted to reconnect zombie connection after disconnecting first (this shouldn't be possible)
    at Object.reconnectCallback (file:///opt/homebrew/lib/node_modules/openclaw/dist/provider-DR2mO1YM.js:13811:26)
    at Timeout.sendHeartbeat [as _onTimeout] (file:///opt/homebrew/lib/node_modules/openclaw/dist/provider-DR2mO1YM.js:13462:12)
    at listOnTimeout (node:internal/timers:605:17)
    at processTimers (node:internal/timers:541:7)

Behaviour

  • Gateway starts successfully
  • After ~60 seconds, the uncaught exception fires in the Telegram provider's heartbeat/reconnect callback
  • Since it's uncaught, the Node.js process exits
  • launchd (macOS, KeepAlive: true, ThrottleInterval: 1) immediately restarts the gateway
  • The cycle repeats indefinitely
  • The Control UI resets every ~60 seconds as a result

Steps to Reproduce

  1. Have Telegram channel configured (channels.telegram.streaming: partial)
  2. Upgrade to 2026.4.5
  3. Start the gateway
  4. Wait ~60 seconds — gateway crashes and restarts
  5. Observe gateway.err.log for the uncaught exception

Environment

  • OpenClaw version: 2026.4.5
  • OS: macOS (arm64, Darwin 25.3.0)
  • Node: v25.8.0
  • Install method: Homebrew (/opt/homebrew/lib/node_modules/openclaw)
  • Gateway mode: local, loopback
  • Telegram streaming: partial
  • Affected since: 2026.4.5 (confirmed working on 2026.4.2)

Workaround

Rolling back to 2026.4.2 resolves the issue:

npm install -g [email protected]

Related

Similar zombie/reconnect crash issues for Discord: #56588, #57291, #54752 — this appears to be the same class of bug now affecting the Telegram provider.

extent analysis

TL;DR

Downgrade to OpenClaw version 2026.4.2 to prevent the gateway from entering a crash-loop due to an uncaught exception in the Telegram provider's reconnect callback.

Guidance

  • Verify that the issue is resolved by downgrading to 2026.4.2 using npm install -g [email protected].
  • Monitor the gateway.err.log for any further uncaught exceptions after downgrading.
  • If the issue persists, review related issues (#56588, #57291, #54752) for potential workarounds or fixes for similar problems with the Discord provider.
  • Consider waiting for a patch release that addresses the reconnect callback issue in the Telegram provider.

Example

No code snippet is provided as the issue is resolved by downgrading the OpenClaw version.

Notes

The root cause of the issue appears to be an uncaught exception in the Telegram provider's reconnect callback, which is introduced in OpenClaw version 2026.4.5. Downgrading to 2026.4.2 is a reliable workaround until a fix is released.

Recommendation

Apply the workaround by downgrading to OpenClaw version 2026.4.2, as it is a reliable and tested solution to prevent the gateway crash-loop.

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…
#autograd error#model save/load#optimization#mixed precision#training loop

Still need to ship something?

×6

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

Back to top recommendations

TRENDING