Ask HN: How do you keep 40+ cron jobs from silently failing?
We are a 6-person team running about 40 cron jobs across three boxes. Twice this quarter one died silently and we found out from a customer. Monitoring feels heavier than the problem. What do small teams actually do?
Why it matters
Named team size, concrete failure mode, quantified pain, and an explicit ask for what small teams do. This is your ICP describing the exact moment they outgrow cron.
Move to make
Reply with a genuinely useful checklist for cron observability at small scale (heartbeat pings, dead-man switches, exit-code capture), then mention how workflow runners make this failure mode structural instead of bolted on.