Skip to content

[Bug] Cron jobs silently lost after upgrading 2026.3.12 → 2026.3.13 — jobs.json not loaded #52569

@witnesssun

Description

@witnesssun

Environment

  • OpenClaw version: 2026.3.13 (61d171a)
  • Previous version: 2026.3.12
  • OS: macOS (arm64)
  • Node: v22.22.0

Problem

After upgrading from 2026.3.12 to 2026.3.13, all cron jobs stopped executing.

openclaw cron status shows:

{"enabled": true, "jobs": 0, "nextWakeAtMs": null}

But ~/.openclaw/cron/jobs.json still contains 10 jobs (mix of enabled/disabled).

Gateway log confirms:

"jobCount":0,"enabledCount":0,"withNextRun":0
"cron: armTimer skipped - no jobs with nextRunAtMs"

Expected

Jobs in jobs.json should be loaded normally after upgrade.

Actual

All jobs silently ignored. nextRunAtMs is null for all jobs, or the cron module fails to parse the schema.

Additional info

  • openclaw doctor --fix did not fix the issue (upgrade tip suggests it should normalize legacy storage)
  • Jobs were last running on 2026-03-20 (the day before upgrade)
  • Last successful cron runs date back to Mar 20 10:01
  • The jobs.json format appears unchanged from 3.12 but 3.13 refuses to load it

Workaround

Manually re-create all jobs via openclaw cron add CLI.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions