Cron Health
Last-run, duration, and outcome for every scheduled job.
Last updated 05/24/26
What this surface does
Cron Health lists every scheduled job with last-run timestamp, duration, outcome (success / failure / running), and the next scheduled run. Sourced from `cron_run_logs` (migration 196).
When to use it
- Morning check — every job should have run within its expected window.
- Investigating "stale data" — is the cron that refreshes the data actually running.
- Post-deploy — confirm no cron silently broke from a code change.
Key gotchas
- A job that has not run in >2 expected intervals is flagged red. A single skipped run is yellow.
- "Running" means a row is open without a completion timestamp. A stuck-running job blocks the next scheduled run.
- Manually retrying a job from this surface acquires the same lock as the scheduled run — never double-trigger.
Related
- Backfill Launcher (manual + historical replay).