Demystifying Cron Expressions: How to Schedule, Debug & Forecast Crontab Jobs

Standard Unix crontab expressions consist of 5 space-delimited fields: `* * * * *` `- - - - -` `| | | | |` `| | | | +----- Day of Week (0 - 6) (Sunday = 0)` `| | | +---------- Month (1 - 12)` `| | +--------------- Day of Month (1 - 31)` `| +-------------------- Hour (0 - 23)` `+------------------------- Minute (0 - 59)` ### Special Characters Cheat Sheet: - `*` (Wildcard): Match every possible value in this field. - `/` (Step Value): Specify increments (e.g. `*/15` in the minute field means every 15 minutes). - `,` (Value List): Match explicit values (e.g. `1,15,30` in the day field). - `-` (Range): Specify inclusive intervals (e.g. `1-5` in the weekday field for Monday through Friday).

The most catastrophic cron bugs occur when developers write a cron schedule assuming local time (e.g. 2:00 AM EST), but the cloud server or Kubernetes cluster executes against Coordinated Universal Time (UTC). Always ensure whether your target environment (AWS EventBridge, GitHub Actions, Linux systemd) interprets cron strings in UTC or local timezone before deploying scheduled tasks.