Version

• OpenClaw: 2026.2.3-1
• Node: v22.12.0
• OS: Windows 10 (x64)

Description

After updating to 2026.2.3, the cron scheduler skips jobs without executing them. The nextWakeAtMs jumps past scheduled job times, causing jobs to never fire.

Reproduction

1. Have multiple cron jobs scheduled throughout the day
2. Gateway running normally
3. Observe that scheduled jobs don't fire
4. Check scheduler status — nextWakeAtMs is set to a time AFTER several scheduled jobs

Evidence

Scheduler status at 11:05 PM on Feb 6:

{
  "enabled": true,
  "jobs": 38,
  "nextWakeAtMs": 1770408000000
}

Job that was skipped:

• habit-course-tracker scheduled for 11:00 PM (cron: 0 23 * * *)
• nextRunAtMs: 1770399000000 (Feb 6, 11:00 PM)
• Job never executed — scheduler's nextWakeAtMs jumped from earlier time directly to 1:30 AM

Timeline:

• Gateway started: Feb 6, 7:33 PM
• All crons from Feb 6 missed (morning, afternoon, evening jobs)
• Scheduler was enabled, jobs were enabled, but nothing fired

What we tried

1. Changed all 38 crons from wakeMode: "next-heartbeat" to wakeMode: "now" — did not fix
2. Verified jobs were enabled and properly configured
3. Manual cron run --jobId <id> returns {"ran": false, "reason": "not-due"}

Expected Behavior

Scheduler should wake at or before each job's nextRunAtMs and execute it.

Actual Behavior

Scheduler's nextWakeAtMs skips past multiple jobs' scheduled times without executing them.

Likely Cause

This started after updating to 2026.2.3. The changelog shows major cron changes:

• "Hard-migrate isolated jobs to announce/none delivery"
• "Deliver announce runs directly, honor delivery mode, and respect wakeMode"
• "Reload store data when store file is recreated"

The nextWakeAtMs calculation logic may have a bug in determining the next wake time.

Workaround

Currently none found. Gateway restart doesn't reliably fix it.

Impact

All scheduled automation (reminders, accountability calls, nightly builds) stopped working.