Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Update button silently no-ops when update.run is coalesced [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#78481•Fetched 2026-05-07 03:36:26
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
2
Author
motacolamotacola
Participants
clawsweeper[bot]clawsweeper[bot]motacolamotacola
Timeline (top)
commented ×1

Error Message

When clicking the Update button in the Control UI while a prior update.run request is already in-flight, the gateway responds with request coalesced (already in-flight) — but the UI gives no feedback. The button stays in its "update available" state with no spinner, error, or confirmation. UI should reflect the coalesced state: show "update in progress", a spinner, or an error/retry prompt so the user knows an update is already underway or has stalled.

Code Example

[restart] request coalesced (already in-flight) reason=update.run actor=openclaw-control-ui
[gateway] update.run restart coalesced ... delayMs=0
RAW_BUFFERClick to expand / collapse

Bug

When clicking the Update button in the Control UI while a prior update.run request is already in-flight, the gateway responds with request coalesced (already in-flight) — but the UI gives no feedback. The button stays in its "update available" state with no spinner, error, or confirmation.

Steps to reproduce

  1. Click the Update button in the Control UI once.
  2. The first update.run gets stuck / partially in-flight (e.g. from a previous failed attempt).
  3. Click the button again.
  4. Nothing visible happens. Button stays the same.

Expected behaviour

UI should reflect the coalesced state: show "update in progress", a spinner, or an error/retry prompt so the user knows an update is already underway or has stalled.

Observed in logs

[restart] request coalesced (already in-flight) reason=update.run actor=openclaw-control-ui
[gateway] update.run restart coalesced ... delayMs=0

Environment

  • OpenClaw 2026.5.4 → 2026.5.5
  • macOS (Apple Silicon)
  • Control UI (webchat vcontrol-ui)

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…
#memory management#API rate limit#retriever error#indexing error#inference speed

Still need to ship something?

×6

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

Back to top recommendations

TRENDING