BlueCheddar

Cron expression explainer

Type a cron expression to read it in plain English and see its next runs in any time zone. It follows the five-field crontab of Linux and Vixie cron, and it runs on your device.

How to check a cron expression

  1. Type the five fields, without the command.
  2. Choose the time zone the machine runs in.
  3. Read the meaning and the next ten runs. Set a start date to see a given day.

Questions

Which cron does this follow?

The five-field crontab of Vixie cron, which most Linux crons descend from: minute, hour, day of month, month and day of week. It takes names such as mon and jan, 7 for Sunday, and nicknames such as @daily. It refuses the seconds field and the ?, L, W and # of Quartz and similar schedulers, and it says why.

What if I set both the day of month and the day of week?

Then either one is enough: 0 0 13 * 5 runs on every 13th and also every Friday. The exception is a field starting with a star. In Vixie cron's source, 0 0 */2 * 1 needs both, so it runs only on Mondays with an odd date. Many other tools read that as either, so the page warns you when your line depends on it. We tested this rule against croniter and read it in the source.

What happens when the clocks change?

Crons differ, so check yours. In this list, a time the clocks jump over moves to the first minute after the jump, with a note, and a time that repeats runs once. A line with a star in the hour field follows real time instead, so it does not move and it runs through both repeated hours. The cronie manual says a job in a skipped hour does not run and a job in a repeated hour runs twice.

Why is 5/15 refused?

Because a crontab takes a step only after a star or a range. Write 5-59/15 to run at 5, 20, 35 and 50 minutes past the hour. A step counts within its own field, so */7 in the minute field restarts at 0 each hour.

Is anything saved or sent?

No. It works on this page alone, with no request and no storage. You can check the page's requests yourself.