Cron Expression Cheat Sheet (2026) — Every Field, Every Shortcut, Every Gotcha

2026-07-17 · By Avinash Kamble, reviewed by Priyanka G.

Every SDET eventually stares at a cron expression like */15 9-17 * * 1-5 and wonders which field is which. This cheat sheet is the reference we keep pinned in Slack — five fields, six fields with seconds, seven with year, plus the shortcuts and gotchas that cost teams a real incident.

POSIX (Linux crontab, GitHub Actions, K8s CronJob, pg_cron, Node-cron, Vercel)
minute       0-59
hour         0-23
day-of-month 1-31
month        1-12  (or JAN-DEC)
day-of-week  0-6   (0=Sun; some engines: 7=Sun)

Quartz (Jenkins Quartz plugin, Spring @Scheduled, Elastic Job)
sec  min  hour  dom  mon  dow  [year]
0    */15  9-17  ?    *    MON-FRI  2026

Gotcha: Quartz requires ? in either dom or dow (they can't both be specified). POSIX has no ?.

*   every value        * * * * *      every minute
,   list               0,15,30,45 * * * *
-   range              0 9-17 * * *   every hour 9am-5pm
/   step               */5 * * * *    every 5 min
L   last (Quartz)      0 0 L * ?      midnight last day of month
W   nearest weekday    0 0 15W * ?    weekday closest to 15th
#   nth weekday        0 0 ? * 2#1    first Monday of month
?   no specific value  used in dom OR dow (Quartz only)

@yearly / @annually  ->  0 0 1 1 *
@monthly             ->  0 0 1 * *
@weekly              ->  0 0 * * 0
@daily / @midnight   ->  0 0 * * *
@hourly              ->  0 * * * *
@reboot              ->  run once at startup (crontab only, NOT K8s)

GitHub Actions and Kubernetes CronJob do not support @reboot. Jenkins pipeline supports @midnight with jitter (spreads jobs across the hour to avoid stampedes).

# Smoke tests every 15 min during business hours, weekdays
*/15 9-17 * * 1-5

# Nightly regression at 2:30 AM
30 2 * * *

# Every Monday 6 AM - weekly report
0 6 * * 1

# First day of month, 00:05 - billing job
5 0 1 * *

# Every 6 hours
0 */6 * * *

# Twice a day (9 AM and 9 PM)
0 9,21 * * *

# Every Sunday at 3:15 AM - cleanup
15 3 * * 0

# Quartz: last Friday of month at 5 PM
0 0 17 ? * 6L

# Quartz: 2nd Tuesday at 10 AM
0 0 10 ? * 3#2

# Every 30 seconds (Quartz)
*/30 * * * * ?

• crontab uses the server timezone. Set CRON_TZ=UTC at the top of the file to make it explicit.
• Kubernetes CronJob was UTC-only until v1.25; now use spec.timeZone: "America/New_York".
• GitHub Actions schedules run in UTC only. There is no timezone option.
• pg_cron uses the database's timezone setting - check with SHOW timezone;.
• Daylight saving: a 0 2 * * * job will run twice on the fall-back day and skip on spring-forward. Use 0 3 * * * if you can't handle that.

Rather than counting stars in a terminal, paste any expression into the free Cron Expression Builder & Tester. It humanises the expression, shows the next 10 run times in your timezone, and exports the exact YAML/Groovy/SQL for Jenkins, GitHub Actions, Kubernetes CronJob, Quartz, Node-cron, pg_cron, Vercel, systemd, and AWS EventBridge.