How to Fix OpenClaw Cron Jobs That Go Silent on Weekends

OpenClaw cron jobs stopped running on 2026-03-28 and 2026-03-29 because schedules used '1-5' (Mon-Fri).

The team identified crons with '0 5 * * 1-5' and updated them to '0 5 * * *' to run every day.

They audited crons, bulk-updated 12 weekday-only jobs, and verified 14+ sessions returned the next day.

Some jobs had accumulated consecutive errors during the silence, causing data and metric gaps.