Check a Cron Job for Drift
Added 2026-11-03
Drift, double runs and missed runs — plan for all three.
Here is a scheduled job's config and logic. Check: 1) whether multiple instances cause duplicate runs; 2) whether long runs delay or skip the next start; 3) whether time zones and daylight saving cause drift; 4) whether failures retry or get compensated; 5) give the minimum fields for a run log that would reveal missed runs; 6) point out where it most easily fails silently.
Site original
Chinese original
How to use
定时任务最危险的不是报错，是不声不响地没跑。
Try tweaking it
- Have it restate requirements and constraints before writing code.
- Ask for the smallest change plus a rollback path, not a full-file rewrite.
What you should get
- A minimal, runnable change with copy-ready code
- Impact list: which files and call sites must follow
Common mistakes
- Asking it to touch ten files at once, then losing track of what broke what.
- Pasting only the error, with no code or version, and getting an unfixable answer.
How to check the output
- The change runs, can be rolled back, and touches nothing unrelated.
- Edge cases (empty, oversized, concurrent) are covered or explained.
Where it works
- Good for: having it restate requirements and constraints, then propose the smallest runnable change.
- Watch out: include versions and a minimal reproduction with the error, or the fix may look plausible but not fit.