openclaw - 💡(How to fix) Fix [Bug]: v2026.4.27 stuck session in one channel blocks all other channels [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#75665Fetched 2026-05-02 05:32:03
View on GitHub
Comments
1
Participants
2
Timeline
9
Reactions
2
Author
Timeline (top)
subscribed ×4mentioned ×3commented ×1cross-referenced ×1

Error Message

[diagnostic] stuck session: sessionId=main state=processing age=624s queueDepth=1
[diagnostic] liveness warning: eventLoopDelayMaxMs=25920.8 eventLoopUtilization=1
[WARN] socket-mode: pong wasn't received within 15000ms
[slack] socket disconnected. retry 1/12 in 2s

Fix Action

Workaround

Rolled back to v2026.4.22 — works normally.

Code Example

[diagnostic] stuck session: sessionId=main state=processing age=624s queueDepth=1
[diagnostic] liveness warning: eventLoopDelayMaxMs=25920.8 eventLoopUtilization=1
[WARN] socket-mode: pong wasn't received within 15000ms
[slack] socket disconnected. retry 1/12 in 2s
RAW_BUFFERClick to expand / collapse

Environment

  • Version: v2026.4.27
  • Node: 22.22.0
  • Provider: Amazon Bedrock
  • Channel: Slack socket mode, multiple channels
  • Per-channel model override via modelByChannel

Symptom

Long-running Bedrock call in one channel causes shared sessionId=main to get stuck (state=processing, age 600s+). All other Slack channels stop responding until Gateway restart.

Event loop blocks for 25+ seconds. Slack WebSocket repeatedly disconnects with pong timeout.

Logs

[diagnostic] stuck session: sessionId=main state=processing age=624s queueDepth=1
[diagnostic] liveness warning: eventLoopDelayMaxMs=25920.8 eventLoopUtilization=1
[WARN] socket-mode: pong wasn't received within 15000ms
[slack] socket disconnected. retry 1/12 in 2s

Steps to reproduce

  1. Configure multiple Slack channels
  2. Set heavier model for one channel via modelByChannel
  3. Trigger a long conversation in that channel
  4. Send messages to other channels in parallel
  5. All channels stop responding

Workaround

Rolled back to v2026.4.22 — works normally.

Regression range

  • Broken: 2026.4.23 ~ 4.29
  • Works: 2026.4.22

Related

#75648, #75610, #75598, #75577, #75516, #75512

extent analysis

TL;DR

Downgrade to version v2026.4.22 to resolve the issue of shared sessionId=main getting stuck and causing all other Slack channels to stop responding.

Guidance

  • The issue seems to be related to a regression introduced in version 2026.4.23, so downgrading to a previous version may help.
  • To verify if the issue is resolved, trigger a long conversation in one channel and send messages to other channels in parallel, checking if all channels respond as expected.
  • If downgrading is not feasible, consider implementing a temporary workaround, such as limiting the number of concurrent conversations or using a lighter model for all channels.
  • Review the related issues (#75648, #75610, #75598, #75577, #75516, #75512) for potential insights into the root cause and possible fixes.

Notes

The exact root cause of the issue is not specified, but it appears to be related to a change introduced in version 2026.4.23. Downgrading to version 2026.4.22 has been confirmed to resolve the issue.

Recommendation

Apply workaround: Downgrade to version v2026.4.22, as it has been confirmed to work normally and resolve the issue.

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…

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]: v2026.4.27 stuck session in one channel blocks all other channels [1 comments, 2 participants]