Background jobs fail silently by design. No exception surfaces. No alert fires. The first sign something is wrong is a user complaint — hours after the damage is done.
Job fails silently
Your backup job throws an error at 2am. No noise.
Hours pass
Users start seeing stale data. You have no idea.
A user complains
That's how you find out. Three hours later.
30-minute postmortem
Digging through logs to find something obvious.
The fix
# Add this at the end of any cron job curl -s https://crondash.dev/ping/YOUR_KEY > /dev/nullIf the ping stops arriving on time, you get a Slack or email alert in under 60 seconds. Not when a user complains. Right when it happens.
Free for 3 monitors. No credit card required.