Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix cron update does not persist changes to jobs.json — Gateway restart reverts changes

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…

Error Message

Alternatively, if this is by design, the cron tool should warn users that changes are not persisted and will be lost on restart.

Fix Action

Workaround

Manually edit cron/jobs.json after each cron update call. A sync script can help:

  • ~/.openclaw/workspace/scripts/cron-jobs-sync.js
RAW_BUFFERClick to expand / collapse

Bug Description

When using the cron tool (via gateway) to update or add a cron job, the changes are applied to the in-memory running state but are not written back to cron/jobs.json.

This means after a Gateway restart, the cron jobs reload from jobs.json and revert to their old values, losing any updates made at runtime.

Steps to Reproduce

  1. Have a cron job in jobs.json with everyMs: 60000
  2. Use cron tool to update it to everyMs: 300000 (5 minutes)
  3. Verify the change works in the running session (cron list shows correct value)
  4. Restart the Gateway
  5. Check jobs.json — the file still shows the old 60000 value
  6. After restart, cron list now shows the old 60000 again

Expected Behavior

Updates made via the cron tool should be persisted to cron/jobs.json so they survive Gateway restarts.

Alternatively, if this is by design, the cron tool should warn users that changes are not persisted and will be lost on restart.

Environment

  • OpenClaw version: 2026.5.7 (eeef486)
  • Gateway running on: WSL2 / Linux 6.6.87.2
  • Node: v22.22.1

Workaround

Manually edit cron/jobs.json after each cron update call. A sync script can help:

  • ~/.openclaw/workspace/scripts/cron-jobs-sync.js

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…
#agent setup#task chaining#parallel task#integration issue#index setup

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 cron update does not persist changes to jobs.json — Gateway restart reverts changes