Lily
Posted on Jul 22
• Originally published at dev.to
This is a continuation of my "Claude Code environment" series. Last time I wrote about making Google Calendar the ground truth for my Vault. This time it's about the timeout hell that hit the same vault-auto-ingest job — and how I climbed out of it with "sub-step idempotency."
When hot.md failed to update three mornings in a row, the cause wasn't "launchd never fired" — it was "launchd fired but the job died partway through." I'd already put the outer retry in place (firing across multiple slots). The problem was on the inside.
