Six Days of a Silent Crash Loop: One Command That Health-Checks 26 launchd Jobs
Losing your job costs you a paycheck. What I didn't expect was to spend that same afternoon discovering that half the automation propping up my side income had quietly stopped running — and nobody, including me, had noticed. Why this setup works Once your personal automation crosses about 20 jobs, "silent death" becomes routine. Human attention has a ceiling. With 3 launchd jobs, you can eyeball…
Six days of a silent crash loop unfolded for the author, who discovered that half of the automation powering his side income had quietly stopped running without anyone noticing. The personal automation system comprised around 26 launchd jobs, and once it exceeded 20 jobs, the chances of unnoticed failure increased significantly.
The author had been earning ¥600,000/month from this system, but when the revenue dropped to zero, they finally noticed the six-day crash loop. Launchd, the daemon-management layer of macOS, responds to crashing scripts by remaining silent and waiting for the next scheduled run, making it difficult to detect issues unless someone manually checks the launchctl list.
The author created automation-health.sh to not only check the health of the system but also fix any problems found immediately. This script examines nine different aspects of the automation setup, including launchd jobs, hook scripts, skill-harvest logs, conversation logs, Obsidian Vault integration, agentmemory server, remember memory layers, disk space, and cron/launchd redundancy.
Any failure in these sections results in an exit status of 1, triggering the StopHook to alert the user. By integrating this script into the StopHook, the user can verify automation health every time they close Claude, ensuring that the system remains operational without requiring manual checks.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
