Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix `openclaw cron` subcommands hang when gateway is busy or degraded; should read local store directly [2 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#75794•Fetched 2026-05-02 05:30:00
View on GitHub
Comments
2
Participants
2
Timeline
3
Reactions
2
Author
JosephMatsikoJosephMatsiko
Participants
clawsweeper[bot]clawsweeper[bot]JosephMatsikoJosephMatsiko
Timeline (top)
commented ×2closed ×1
RAW_BUFFERClick to expand / collapse

openclaw cron list / add / rm all proxy through the gateway via WebSocket. When the gateway is busy (high eventLoopDelayMaxMs, plugin warmup, channel auto-restart loop, MCP server initialization), every cron subcommand hangs indefinitely waiting for the round-trip.

Reproduce:

  1. Configure 16+ MCP servers in mcp.servers (typical "kitchen sink" setup of an openclaw user with multiple toolkits).
  2. While gateway is in plugin-warmup phase or channel auto-restart loop, run openclaw cron list. Observe: hangs >60s.

Why it matters: openclaw cron is supposed to be the "lightweight operator tool" — it should answer in milliseconds whether the gateway is healthy or not. The current dependency on a healthy gateway makes it unusable exactly when the operator needs it most (during a degradation event).

Proposed fix: cron schedules live in a local SQLite or JSON file the gateway also reads/writes. openclaw cron list should be able to read that store directly without any WebSocket call. Mutations (add/rm) should either:

  • Write to the local store and emit a SIGHUP / file-watch signal to the gateway to pick up changes
  • OR fall back to local-only mutation when the gateway is unreachable, with a clear log line

The principle: control-plane operations should not depend on data-plane health.

extent analysis

TL;DR

Implement a local storage solution for cron schedules, allowing openclaw cron list to read directly without relying on a WebSocket call to the gateway.

Guidance

  • Identify the local storage solution (SQLite or JSON file) and ensure it is properly configured and accessible.
  • Modify the openclaw cron list command to read from the local storage instead of relying on the gateway.
  • For mutations (add/rm), consider implementing a fallback mechanism to write to the local store and emit a signal to the gateway when it becomes available.
  • Verify that the proposed fix does not introduce any data consistency issues between the local store and the gateway.

Example

# Example of how openclaw cron list could read from local storage
openclaw cron list --local-storage /path/to/schedules.db

Notes

The proposed fix assumes that the local storage solution is already implemented and functional. Additional considerations may be needed to ensure data consistency and handle edge cases.

Recommendation

Apply workaround: Implement a local storage solution for cron schedules to decouple control-plane operations from data-plane health, allowing for more reliable and responsive openclaw cron commands.

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…
#optimization#mixed precision#training loop#device allocation#model download

Still need to ship something?

×6

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

Back to top recommendations

TRENDING