I ran 1,000+ unattended agent-hours. These 6 failure patterns repeat every time.

Unattended automation fails in patterns, not surprises. After auditing month after month of overnight runs (outward contacts, publishing rails, form campaigns, monitoring loops), six failure patterns show up again and again — and all six are fixable with about an hour of work.

Pattern 1: The phantom success

The script exits 0. Nothing happened. Exit codes are a claim, not proof. The fix: every successful step must WRITE an artifact — a file, a row, an API response code. No artifact, no success. This single rule cut our "silent failure" class to zero.

Pattern 2: Health checks that ping the wrong layer

"Server is up" tells you nothing if the API token expired at midnight. Test the full path: authenticate, read one real record, stop. That probe catches dead credentials, dead DNS, and dead quota — the three midnight killers.

Pattern 3: Retry loops with no ceiling

A retry loop without a cap is a money pump. Cap retries per step, cap steps per run, and when the cap trips: stop and escalate with a full attempt log. Flailing is worse than failing.

Pattern 4: The missing middle tier

Most automation has tier 1 (retry) and tier 3 (crash). Nobody builds tier 2: degrade and continue with reduced capability while logging loudly. Tier 2 is the difference between a hiccup and an outage — one degraded-but-live run keeps the mission moving while the failed leg gets fixed.

Pattern 5: Evidence you cannot audit in 5 minutes

If your morning review takes 20 minutes, you built a report, not an audit. One command, one page: started / finished / failed, outward contacts made, money spent vs budget, oldest unresolved failure. If any line is missing, your monitoring is theater.

Pattern 6: Nobody watches the watcher

Your monitor script can die too — cron can be killed, the laptop can sleep, the token can rotate. Run an independent second probe on a different path whose only job is to confirm it can see the first probe. If it can't, that's the real alert.

---

None of this is exotic. It's boring discipline — the kind that compounds. The same rules keep a fleet of autonomous agents honest 24/7 with no human awake.

If you want the shortcuts: the free 1-page first-30-minutes incident checklist (no email needed), and the full 25-script unattended-ops toolkit in the Agent Ops Mega Bundle. Working samples on GitHub.