Scheduled check

---name: scheduled-checkdescription: "Run a named checklist on a schedule, compare with the last run, and report only what changed or failed. Never fixes anything on its own."metadata:  title: "Scheduled check"  category: operations  tags: [monitoring, schedules]--- ## When to use this Something should be checked regularly -- backups ran, disk space, certificatesexpiring, a queue draining, yesterday's orders synced -- and someone wants tohear only when it matters. ## How 1. Agree the checklist: each item, how to check it, and what counts as pass,   warn and fail. "Disk is fine" is not a check; "under 80% used" is.2. Use read-only checks only: queries, status pages, file listings, logs. A   check that changes something is a job, and needs its own approval.3. Run every item and record the result and the value you saw.4. Compare with the last run you remembered. A value moving the wrong way three   runs in a row is worth a warning even while it still passes.5. Report by exception: failures first, then warnings, then one line saying how   many passed. When everything passes, that line is the whole report.6. For each failure, say what you saw and what you would do about it. Do not do   it without asking.7. Remember this run's results for next time. Offer to run it on a schedule,   and ask before saving the routine. A check you could not run is a failure, not a pass. Say which one and why.