Bug Description

Cron jobs stop executing in versions 2026.2.3 and 2026.2.3-1. The scheduler correctly advances nextRunAtMs when scheduled times pass, but jobs are never actually executed.

Environment

• OpenClaw version: 2026.2.3-1 (broken), 2026.2.2 (working)
• OS: Ubuntu 22.04 (AWS EC2)
• Node: v22.22.0

Symptoms

• lastRunAtMs remains unchanged even as nextRunAtMs advances
• Multiple gateway restarts don't fix the issue
• Deleting and recreating jobs doesn't fix the issue
• Downgrading to 2026.2.2 immediately fixes the issue

Steps to Reproduce

1. Install [email protected]
2. Create a cron job with sessionTarget: isolated and schedule: { kind: 'cron', expr: '*/3 * * * *' }
3. Wait for scheduled time to pass
4. Observe: nextRunAtMs advances to next slot but lastRunAtMs never updates

Expected Behavior

Jobs should execute when their scheduled time arrives.

Actual Behavior

Scheduler advances nextRunAtMs but never triggers job execution. Jobs appear stuck.

Workaround

Downgrade to 2026.2.2:

npm install -g [email protected]
systemctl --user restart openclaw-gateway

Logs

Cron module starts correctly:

cron: started {enabled: true, jobs: 19, nextWakeAtMs: 1770342600000}

But no job execution logs appear when scheduled times pass.