Bug

After a cron job of kind agentTurn completes, the running_at_ms field in the cron_jobs SQLite table is not reset to 0. On the next scheduled wake, the gateway sees running_at_ms > 0, assumes the job is still running, and skips execution.

Environment

• OpenClaw 2026.6.11
• Node v22.22.3
• Debian 13

Steps

1. Create a cron with session_target: isolated and payload_kind: agentTurn at */10 * * * *
2. Let it run once
3. running_at_ms stays with a timestamp > 0
4. Cron never fires again

Workaround

UPDATE cron_jobs SET running_at_ms = 0 WHERE job_id = ? + gateway restart