Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Raspberry Pi Slack gateway latency regression after 2026.4.21 [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#75872•Fetched 2026-05-02 05:28:39
View on GitHub
Comments
2
Participants
3
Timeline
11
Reactions
2
Author
neeravmakwananeeravmakwana
Participants
clawsweeper[bot]clawsweeper[bot]hexspritehexspriteneeravmakwananeeravmakwana
Timeline (top)
cross-referenced ×7commented ×2labeled ×2

Follow up to issue #75872.

Peter closed #75872 noting fixes on main and asking for fresh traces from 61fc62ade7 or newer if Slack-on-Pi still missed pongs.

On OpenClaw 2026.5.5 (b1abf9d) / Raspberry Pi / Slack Socket Mode, we still see:

  • socket-mode ping timeout (30000ms) and [slack] socket disconnected
  • [health-monitor] … restarting (reason: disconnected)
  • [diagnostic] liveness warning with multi-second eventLoopDelayMaxMs while agent:gemini:slack:channel:… or concurrent dashboard work is active
  • Occasional incomplete turn … payloads=0 for Slack-delivered turns

Detailed traces/ timelines in the additional details section

Error Message

May 06 08:52:10 raspberrypi node[117906]: 2026-05-06T08:52:10.862-04:00 [agent/embedded] incomplete turn detected: ... stopReason=stop payloads=0 — surfacing error to user

Root Cause

Follow up to issue #75872.

Peter closed #75872 noting fixes on main and asking for fresh traces from 61fc62ade7 or newer if Slack-on-Pi still missed pongs.

On OpenClaw 2026.5.5 (b1abf9d) / Raspberry Pi / Slack Socket Mode, we still see:

  • socket-mode ping timeout (30000ms) and [slack] socket disconnected
  • [health-monitor] … restarting (reason: disconnected)
  • [diagnostic] liveness warning with multi-second eventLoopDelayMaxMs while agent:gemini:slack:channel:… or concurrent dashboard work is active
  • Occasional incomplete turn … payloads=0 for Slack-delivered turns

Detailed traces/ timelines in the additional details section

Fix Action

Fix / Workaround

Frequency: Multiple observed Slack messages on the affected Pi setup showed multi-minute latency before downgrade. The per-message ensureOpenClawModelsJson(...) delay was directly observed on 2026.4.21 before the fast-path workaround.

Code Example

Copied from the gateway host; timestamps are **gateway local** (`-04:00`).


May 06 08:46:15 raspberrypi node[117408]: 2026-05-06T08:46:15.986-04:00 [diagnostic] liveness warning: reasons=event_loop_delay interval=35s eventLoopDelayP99Ms=27.1 eventLoopDelayMaxMs=5960.1 eventLoopUtilization=0.581 cpuCoreRatio=0.665 active=1 waiting=0 queued=1 phase=channels.slack.start-account ... work=[active=agent:gemini:slack:channel:c0agmgx2r26(processing,q=1,age=19s) ...]
May 06 08:46:44 raspberrypi node[117408]: 2026-05-06T08:46:44.537-04:00 [agent/embedded] [trace:embedded-run] prep stages: ... phase=stream-ready totalMs=14355 stages=...core-plugin-tools:2918ms...bundle-tools:3895ms...system-prompt:3572ms...stream-setup:3223ms@14355
May 06 08:46:45 raspberrypi node[117408]: 2026-05-06T08:46:45.984-04:00 [diagnostic] liveness warning: reasons=event_loop_delay,event_loop_utilization,cpu interval=30s eventLoopDelayP99Ms=7495.2 eventLoopDelayMaxMs=12322.9 eventLoopUtilization=0.964 cpuCoreRatio=1.027 ... work=[active=agent:gemini:slack:channel:c0agmgx2r26(processing/model_call,q=1,age=1s last=model_call:started) ...]
May 06 08:51:22 raspberrypi node[117906]: 2026-05-06T08:51:22.878-04:00 [diagnostic] liveness warning: ... eventLoopDelayMaxMs=6165.6 ... work=[active=agent:gemini:slack:channel:c0agmgx2r26(processing,q=1,age=6s) ...]
May 06 08:51:53 raspberrypi node[117906]: 2026-05-06T08:51:53.410-04:00 [diagnostic] liveness warning: ... eventLoopDelayP99Ms=12490.6 eventLoopDelayMaxMs=12490.6 eventLoopUtilization=1 cpuCoreRatio=1.075 ... work=[active=agent:gemini:slack:channel:c0agmgx2r26(processing,q=1,age=36s) ...]
May 06 08:52:04 raspberrypi node[117906]: 2026-05-06T08:52:04.779-04:00 [agent/embedded] [trace:embedded-run] prep stages: ... phase=stream-ready totalMs=14363 ...
May 06 08:52:10 raspberrypi node[117906]: 2026-05-06T08:52:10.862-04:00 [agent/embedded] incomplete turn detected: ... stopReason=stop payloads=0 — surfacing error to user
May 06 09:27:45 raspberrypi node[120901]: 2026-05-06T09:27:45.749-04:00 [diagnostic] liveness warning: reasons=event_loop_delay,cpu interval=49s eventLoopDelayP99Ms=4144 eventLoopDelayMaxMs=37581 eventLoopUtilization=0.949 cpuCoreRatio=0.992 ... work=[active=agent:gemini:dashboard:56722ea3-c65b-42b9-94cd-b0f13a0ba7da(processing/tool_call,q=1,age=48s last=tool:web_search:started) ...]
May 06 09:27:45 raspberrypi node[120901]: socket-mode:socket-mode A ping wasn't received from the server before the timeout of 30000ms!
May 06 09:27:45 raspberrypi node[120901]: 2026-05-06T09:27:45.761-04:00 [slack] socket disconnected (disconnect); reconnecting in 2s (attempt 1/12)
May 06 09:27:54 raspberrypi node[120901]: 2026-05-06T09:27:54.175-04:00 [health-monitor] [slack:default] health-monitor: restarting (reason: disconnected)
May 06 09:28:56 raspberrypi node[120901]: 2026-05-06T09:28:56.133-04:00 [diagnostic] liveness warning: ... eventLoopDelayMaxMs=21273.5 ... work=[active=agent:gemini:dashboard:56722ea3-c65b-42b9-94cd-b0f13a0ba7da(processing/tool_call,q=1,age=118s last=tool:exec:ended) ...]
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Follow up to issue #75872.

Peter closed #75872 noting fixes on main and asking for fresh traces from 61fc62ade7 or newer if Slack-on-Pi still missed pongs.

On OpenClaw 2026.5.5 (b1abf9d) / Raspberry Pi / Slack Socket Mode, we still see:

  • socket-mode ping timeout (30000ms) and [slack] socket disconnected
  • [health-monitor] … restarting (reason: disconnected)
  • [diagnostic] liveness warning with multi-second eventLoopDelayMaxMs while agent:gemini:slack:channel:… or concurrent dashboard work is active
  • Occasional incomplete turn … payloads=0 for Slack-delivered turns

Detailed traces/ timelines in the additional details section

Steps to reproduce

  1. Install the latest OpenClaw on Raspberry Pi
  2. Complete the setup by adding appropriate channels and models
  3. Ensure that a narrow set of plugins is enabled
  4. Send a message on slack to the bot
  5. Observe the latency/ traces

Expected behavior

In 2026.4.21 and prior versions, the latency is very small. Replies are received in the next minute or even the same minute.

Actual behavior

In 2026.4.22 and all subsequent versions, there is a huge latency in receiving the response on the Raspberry Pi. While limited resources on the Pi are one of the contributors to this problem, it does not seem like the only reason for this latency. 2026.4.21 and prior versions work fine on the same device.

OpenClaw version

2.26.5.5

Operating system

Raspberri Pi OS

Install method

npm global install, running via openclaw-gateway.service

Model

google/gemini-2.5-flash

Provider / routing chain

openclaw -> google/gemini-2.5-flash via direct Google Gemini API (google-generative-ai)

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Copied from the gateway host; timestamps are **gateway local** (`-04:00`).


May 06 08:46:15 raspberrypi node[117408]: 2026-05-06T08:46:15.986-04:00 [diagnostic] liveness warning: reasons=event_loop_delay interval=35s eventLoopDelayP99Ms=27.1 eventLoopDelayMaxMs=5960.1 eventLoopUtilization=0.581 cpuCoreRatio=0.665 active=1 waiting=0 queued=1 phase=channels.slack.start-account ... work=[active=agent:gemini:slack:channel:c0agmgx2r26(processing,q=1,age=19s) ...]
May 06 08:46:44 raspberrypi node[117408]: 2026-05-06T08:46:44.537-04:00 [agent/embedded] [trace:embedded-run] prep stages: ... phase=stream-ready totalMs=14355 stages=...core-plugin-tools:2918ms...bundle-tools:3895ms...system-prompt:3572ms...stream-setup:3223ms@14355
May 06 08:46:45 raspberrypi node[117408]: 2026-05-06T08:46:45.984-04:00 [diagnostic] liveness warning: reasons=event_loop_delay,event_loop_utilization,cpu interval=30s eventLoopDelayP99Ms=7495.2 eventLoopDelayMaxMs=12322.9 eventLoopUtilization=0.964 cpuCoreRatio=1.027 ... work=[active=agent:gemini:slack:channel:c0agmgx2r26(processing/model_call,q=1,age=1s last=model_call:started) ...]
May 06 08:51:22 raspberrypi node[117906]: 2026-05-06T08:51:22.878-04:00 [diagnostic] liveness warning: ... eventLoopDelayMaxMs=6165.6 ... work=[active=agent:gemini:slack:channel:c0agmgx2r26(processing,q=1,age=6s) ...]
May 06 08:51:53 raspberrypi node[117906]: 2026-05-06T08:51:53.410-04:00 [diagnostic] liveness warning: ... eventLoopDelayP99Ms=12490.6 eventLoopDelayMaxMs=12490.6 eventLoopUtilization=1 cpuCoreRatio=1.075 ... work=[active=agent:gemini:slack:channel:c0agmgx2r26(processing,q=1,age=36s) ...]
May 06 08:52:04 raspberrypi node[117906]: 2026-05-06T08:52:04.779-04:00 [agent/embedded] [trace:embedded-run] prep stages: ... phase=stream-ready totalMs=14363 ...
May 06 08:52:10 raspberrypi node[117906]: 2026-05-06T08:52:10.862-04:00 [agent/embedded] incomplete turn detected: ... stopReason=stop payloads=0 — surfacing error to user
May 06 09:27:45 raspberrypi node[120901]: 2026-05-06T09:27:45.749-04:00 [diagnostic] liveness warning: reasons=event_loop_delay,cpu interval=49s eventLoopDelayP99Ms=4144 eventLoopDelayMaxMs=37581 eventLoopUtilization=0.949 cpuCoreRatio=0.992 ... work=[active=agent:gemini:dashboard:56722ea3-c65b-42b9-94cd-b0f13a0ba7da(processing/tool_call,q=1,age=48s last=tool:web_search:started) ...]
May 06 09:27:45 raspberrypi node[120901]: socket-mode:socket-mode A ping wasn't received from the server before the timeout of 30000ms!
May 06 09:27:45 raspberrypi node[120901]: 2026-05-06T09:27:45.761-04:00 [slack] socket disconnected (disconnect); reconnecting in 2s (attempt 1/12)
May 06 09:27:54 raspberrypi node[120901]: 2026-05-06T09:27:54.175-04:00 [health-monitor] [slack:default] health-monitor: restarting (reason: disconnected)
May 06 09:28:56 raspberrypi node[120901]: 2026-05-06T09:28:56.133-04:00 [diagnostic] liveness warning: ... eventLoopDelayMaxMs=21273.5 ... work=[active=agent:gemini:dashboard:56722ea3-c65b-42b9-94cd-b0f13a0ba7da(processing/tool_call,q=1,age=118s last=tool:exec:ended) ...]

Impact and severity

Affected: Raspberry Pi Slack gateway users on newer 2026.4.x versions after 2026.4.21.

Severity: High for always-on Slack gateway use on resource-constrained hardware.

Frequency: Multiple observed Slack messages on the affected Pi setup showed multi-minute latency before downgrade. The per-message ensureOpenClawModelsJson(...) delay was directly observed on 2026.4.21 before the fast-path workaround.

Consequence: Slack replies were delayed by minutes and Slack Socket Mode missed pongs during gateway preparation windows, making the bot feel unreliable.

Additional information

2026.4.21 is the last known good version. I have faced this issue on the latest OpenClaw multiple times. And each time, downgrading to 2026.4.21 has solved the issue.

extent analysis

TL;DR

The most likely fix for the multi-minute delay in Slack replies on Raspberry Pi Slack gateways is to backport the fast model resolution path from newer OpenClaw versions to the affected version, allowing for non-blocking model resolution.

Guidance

  • Investigate the introduction of heavier bundled plugin runtime root/mirror behavior in versions after 2026.4.21 and its impact on gateway responsiveness.
  • Consider implementing a low-resource gateway mode that avoids expensive plugin/provider/model discovery during normal message handling.
  • Backport the fast model resolution path to the affected version to prevent ensureOpenClawModelsJson(...) from blocking the message path.
  • Verify the fix by checking for missed Slack pongs and measuring the response time of Slack replies.

Example

No code example is provided as the issue suggests backporting existing code from newer versions.

Notes

The investigation suggests two separate performance concerns: the introduction of heavier bundled plugin runtime root/mirror behavior and the blocking ensureOpenClawModelsJson(...) call. Addressing both concerns may be necessary to fully resolve the issue.

Recommendation

Apply the workaround by backporting the fast model resolution path to the affected version, as it has been shown to remove the ensureOpenClawModelsJson(...) delay from the warm Slack message path. This should improve the responsiveness of the Slack gateway on low-resource devices.

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

In 2026.4.21 and prior versions, the latency is very small. Replies are received in the next minute or even the same minute.

#api#database connection#vector store#embedding generation#cache error

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]: Raspberry Pi Slack gateway latency regression after 2026.4.21 [2 comments, 3 participants]