Cron expression explainer
Paste a cron schedule and see what it means in plain English, with its next run times in UTC. Works with crontab, GitHub Actions, Kubernetes CronJobs and most job schedulers.
Questions
What are the five fields?
Minute (0–59), hour (0–23), day of the month (1–31), month (1–12 or JAN–DEC) and day of the week (0–6 or SUN–SAT, where 0 and 7 are both Sunday). For example
30 9 * * 1-5 runs at 09:30 on weekdays.What do * , - and / mean?
* means every value, , lists values (9,17), - is a range (1-5) and / is a step (*/15 is every 15 minutes). Shortcuts like @daily and @hourly work too.Which time zone does cron use?
Usually the server’s time zone. GitHub Actions and most cloud schedulers use UTC, which is what the run times above are in. If your server runs in another zone, shift them by its offset.
Why did my job run on an unexpected day?
When you set both the day of the month and the day of the week, cron runs the job when either one matches, not both. 0 0 1 * 5 runs on the 1st of every month and also on every Friday.
How do I know when a cron job stops running?
Ping a heartbeat URL at the end of the job, for example
curl -fsS https://downbell.app/h/your-token. If the ping doesn’t arrive on time, Downbell alerts you by phone, email, Slack or Telegram. For GitHub Actions there’s a ready-made heartbeat action.