"My database backup script broke 11 days before I found out. Credentials got rotated, pg_dump started erroring, and cron just kept running it on schedule like nothing was wrong. No email. No alert. Eleven days of no backups. I only found out because I needed to restore something." Sound familiar? If you've run cron jobs in production, you've probably been here. Cron doesn't know your job failed
Your Cron Jobs Are Silently Failing. Here's How to Know in 30 Seconds.
Pytheas·Dev.to··1 min read
D
Continue reading on Dev.to
This article was sourced from Dev.to's RSS feed. Visit the original for the complete story.