Skip to content

[Critical] Cron scheduler completely unresponsive on latest version (even with manual wake) #9575

@smturtle2

Description

@smturtle2

Summary:
The cron scheduler is failing to execute any jobs automatically. While jobs are registered correctly and appear in the cron list, the scheduler does not fire at the scheduled nextRunAtMs. Manual cron run works, but the automated loop seems dead.

Environment:

  • OpenClaw version: Latest
  • OS: Linux 6.6.87.2-microsoft-standard-WSL2 (x64)
  • Runtime: Node v24.13.0

Symptoms:

  1. Created a recurring job (every: 60000) but it never executes.
  2. cron status shows a nextWakeAtMs in the past or far future that doesn't update.
  3. Calling cron(action="wake", mode="now") returns { ok: true } but does NOT trigger pending jobs.
  4. Manually checking jobs.json shows the jobs exist and are enabled, but the state.nextRunAtMs is ignored by the engine.
  5. Even after a gateway restart, the scheduler remains stuck.

Reproducibility:
Consistent. Every new session and every new job fails to trigger automatically. This renders the automation capabilities of OpenClaw unusable.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions