# scheduled-jobs-failing

Idea IB-0318. Status: DRAFT, nothing posted.

## Slides

**Cover.** 9 of my scheduled jobs were failing. My own health report said so. Nothing had told me. (report dated 5 Oct 2026)

**Slide 2.** Automation does not tell you when it dies. A job that fails quietly looks the same as one that works.

**Slide 3.** Data. 9 marked FAIL, 1 marked STALE, report dated 5 Oct 2026.

**Slide 4.** Two kinds of broken. A crash exits non-zero. A quiet job just stops talking.

**Slide 5.** One alert may not be a crash. A weekly check can exit 1 because it fired, not because it broke.

**Slide 6.** The weekly check: list every job and last exit code, compare last run to schedule, mark FAIL, STALE or OK, read the log before calling a FAIL a crash, overwrite the report.

**Slide 7.** Quote. If nothing tells you it failed, assume nothing is telling you.

**Slide 8.** Comment FLEET for the health-check rules plus the free Fleet Room invite.

## Claims and sources

| Claim | Source | Read-date | Note |
|---|---|---|---|
| 9 jobs FAIL, 1 STALE | Cron health report, fired 2026-10-05 | 2026-10-11 | Perishable; re-read live before any shoot |
| (31 total dropped) | IB-0318 title only; the 5 Oct report does not state a total and LaunchAgents count today is 35 to 37 | 2026-10-11 | removed by conductor, unverifiable |
| Some alerts may not be crashes | Same report, one row reads "MAY be a fired alert, not a crash" | 2026-10-11 | |
| One job marked STALE though loaded | Same report | 2026-10-11 | Quiet job, not stopped |