What is a Cron Job?

A cron schedule is typically expressed as five fields representing minute, hour, day of month, month, and day of week, letting a task run anywhere from every minute to once a year on a specific date. This is the underlying mechanism behind a huge share of automated background work: nightly database backups, weekly report generation, periodic health checks, and scheduled reminders all commonly run as cron jobs somewhere in a system's infrastructure. The reliability challenges are less about the scheduling syntax and more about what happens around it: what happens if a job is still running when its next scheduled run comes due, whether a missed run (say, because the server was down) gets caught up or silently skipped, and how failures get surfaced rather than failing silently in a log nobody reads. Production cron systems typically add locking to prevent overlapping runs and alerting so a failed job doesn't go unnoticed for days. Cron-based scheduling has extended well beyond server infrastructure into product features — scheduled reports, recurring reminders, and periodic AI agent tasks all commonly use the same underlying cron-style scheduling under the hood.