Cron Expressions Explained: From Basics to Advanced Scheduling

Why Every Developer Needs to Understand Cron Automated scheduling is fundamental to modern software operations. Whether you are rotating logs on a Linux server, triggering a CI pipeline, or scaling pods in Kubernetes, cron expressions are the lingua franca that tells a system when to act. Despite their compact syntax, cron expressions trip up even experienced engineers. An off-by-one in the day-of-week field can mean the difference between a nightly backup and a silent data loss. This guide walks you through the syntax, demonstrates common patterns across real-world environments, and provides a cheat sheet you can bookmark for daily reference. Anatomy of a Cron Expression The Standard 5-Field Format The classic Unix crontab uses five space-separated fields: ┌───────────── minute (0-59) │ ┌───────────── hour (0-23) │ │ ┌───────────── day of month (1-31) │ │ │ ┌───────────── month (1-12 or JAN-DEC) │ │ │ │ ┌───────────── day of week (0-7, where 0 and 7 = Sunday, or SUN-SAT) │ │ │ │ │ * *