Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: /stop doesn't work after upgrading to 2025.5.12

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…

After upgrading to 2025.5.12 it appears that /stop no longer stops prompts. I'm issuing /stop from Telegram

Error Message

warn warn warn warn warn

Root Cause

After upgrading to 2025.5.12 it appears that /stop no longer stops prompts. I'm issuing /stop from Telegram

Code Example

23:01:23
warn
diagnostic
liveness warning: reasons=event_loop_delay,event_loop_utilization,cpu interval=37s eventLoopDelayP99Ms=14134.8 eventLoopDelayMaxMs=14134.8 eventLoopUtilization=0.995 cpuCoreRatio=1.036 active=1 waiting=0 queued=2 phase=channels.telegram.start-account recentPhases=sidecars.main-session-recovery:6ms,sidecars.restart-sentinel:98ms,post-attach.update-sentinel:77ms,sidecars.session-locks:1103ms,post-ready.maintenance:11ms,sidecars.model-prewarm:2703ms work=[active=agent:lead-scout:telegram:direct:6938637819(processing,q=2,age=16s) queued=agent:lead-scout:telegram:direct:6938637819(processing,q=2,age=16s)]
23:01:23
warn
fetch-timeout
fetch timeout reached; aborting operation
23:01:23
warn
diagnostic
liveness warning: reasons=event_loop_delay,event_loop_utilization,cpu interval=37s eventLoopDelayP99Ms=14134.8 eventLoopDelayMaxMs=14134.8 eventLoopUtilization=0.995 cpuCoreRatio=1.036 active=1 waiting=0 queued=2 phase=channels.telegram.start-account recentPhases=sidecars.main-session-recovery:6ms,sidecars.restart-sentinel:98ms,post-attach.update-sentinel:77ms,sidecars.session-locks:1103ms,post-ready.maintenance:11ms,sidecars.model-prewarm:2703ms work=[active=agent:lead-scout:telegram:direct:6938637819(processing,q=2,age=16s) queued=agent:lead-scout:telegram:direct:6938637819(processing,q=2,age=16s)]
23:01:23
warn
fetch-timeout
fetch timeout reached; aborting operation
23:01:26
warn
agent/embedded
[trace:embedded-run] prep stages: runId=73e075d7-8681-4221-85cf-361e17e53cf1 sessionId=630e1817-5fbf-46d0-bd8e-aadcaa6c0f3c phase=stream-ready totalMs=21492 stages=workspace-sandbox:3ms@3ms,skills:0ms@3ms,core-plugin-tools:390ms@393ms,bootstrap-context:59ms@452ms,bundle-tools:19660ms@20112ms,system-prompt:1200ms@21312ms,session-resource-loader:77ms@21389ms,agent-session:7ms@21396ms,stream-setup:96ms@21492ms
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After upgrading to 2025.5.12 it appears that /stop no longer stops prompts. I'm issuing /stop from Telegram

Steps to reproduce

Start a prompt, then issue /stop

Expected behavior

The prompt should stop immediately

Actual behavior

Nothing happens the prompt continues

OpenClaw version

2025.5.12

Operating system

Ubuntu

Install method

No response

Model

qwen3.6

Provider / routing chain

lmstudio

Additional provider/model setup details

No response

Logs, screenshots, and evidence

23:01:23
warn
diagnostic
liveness warning: reasons=event_loop_delay,event_loop_utilization,cpu interval=37s eventLoopDelayP99Ms=14134.8 eventLoopDelayMaxMs=14134.8 eventLoopUtilization=0.995 cpuCoreRatio=1.036 active=1 waiting=0 queued=2 phase=channels.telegram.start-account recentPhases=sidecars.main-session-recovery:6ms,sidecars.restart-sentinel:98ms,post-attach.update-sentinel:77ms,sidecars.session-locks:1103ms,post-ready.maintenance:11ms,sidecars.model-prewarm:2703ms work=[active=agent:lead-scout:telegram:direct:6938637819(processing,q=2,age=16s) queued=agent:lead-scout:telegram:direct:6938637819(processing,q=2,age=16s)]
23:01:23
warn
fetch-timeout
fetch timeout reached; aborting operation
23:01:23
warn
diagnostic
liveness warning: reasons=event_loop_delay,event_loop_utilization,cpu interval=37s eventLoopDelayP99Ms=14134.8 eventLoopDelayMaxMs=14134.8 eventLoopUtilization=0.995 cpuCoreRatio=1.036 active=1 waiting=0 queued=2 phase=channels.telegram.start-account recentPhases=sidecars.main-session-recovery:6ms,sidecars.restart-sentinel:98ms,post-attach.update-sentinel:77ms,sidecars.session-locks:1103ms,post-ready.maintenance:11ms,sidecars.model-prewarm:2703ms work=[active=agent:lead-scout:telegram:direct:6938637819(processing,q=2,age=16s) queued=agent:lead-scout:telegram:direct:6938637819(processing,q=2,age=16s)]
23:01:23
warn
fetch-timeout
fetch timeout reached; aborting operation
23:01:26
warn
agent/embedded
[trace:embedded-run] prep stages: runId=73e075d7-8681-4221-85cf-361e17e53cf1 sessionId=630e1817-5fbf-46d0-bd8e-aadcaa6c0f3c phase=stream-ready totalMs=21492 stages=workspace-sandbox:3ms@3ms,skills:0ms@3ms,core-plugin-tools:390ms@393ms,bootstrap-context:59ms@452ms,bundle-tools:19660ms@20112ms,system-prompt:1200ms@21312ms,session-resource-loader:77ms@21389ms,agent-session:7ms@21396ms,stream-setup:96ms@21492ms

Impact and severity

At least telegram users

Additional information

Worked fine in 2025.5.7

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

The prompt should stop immediately

#indexing error#inference speed#output truncation#response parsing#generation 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]: /stop doesn't work after upgrading to 2025.5.12