What the expression does
*/5 * * * * runs the command at minutes 0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50 and 55 of every hour — 288 times per day.
The step value */5 means “every fifth value starting at the minimum”. It is equivalent to 0-59/5. The hour, day, month and weekday fields remain unrestricted.
When this schedule is useful
- Polling an external API with a rate limit that resets per minute.
- Checking a queue depth or backlog every five minutes.
- Refreshing a cache or materialized view that tolerates five minutes of staleness.
- Heartbeat jobs that must detect failure quickly without hammering the target.
Nearby expressions worth knowing
Small changes to one field produce very different schedules. These variants are the ones people usually want when they search for this cadence:
- Every 5 min, offset to :02:
2-59/5 * * * *— Fires at :02, :07, :12 … avoiding the top of the hour. - Every 3 minutes:
*/3 * * * *— 480 runs/day; make sure the upstream allows it. - Every 15 minutes:
*/15 * * * *— The usual choice for low-priority sync jobs. - Every 5 min, business hours:
*/5 9-17 * * 1-5— Only during weekday working hours.
2-59/5 * * * * # Every 5 min, offset to :02
*/3 * * * * # Every 3 minutes
*/15 * * * * # Every 15 minutes
*/5 9-17 * * 1-5 # Every 5 min, business hoursTimezone, load and edge cases
Cron evaluates this expression in the timezone of the daemon, not the timezone of the person who wrote it. If the server runs UTC, a schedule that looks like a morning job can fire in the middle of the local night. Select the server timezone in the next-run preview and compare the wall-clock time before deploying.
*/5 is anchored to minute 0, not to when you saved the crontab. Saving at 12:03 does not shift the schedule to :03, :08, :13.
A five-minute job that occasionally takes six minutes overlaps. Use a lock file if double execution is harmful.
All servers in a fleet hit the API at the same seconds; stagger the minute field per host if the upstream rate limit is shared.
If the schedule runs more often than you expect, check whether day-of-month and day-of-week are both restricted — Vixie cron treats that combination as OR, not AND.
Verify it before shipping
- Run the expression through the explainer and read the English sentence once.
- Check the next five run times in the server's timezone, not your laptop's.
- Execute the command manually with the same user and environment cron will use.
- Redirect stdout and stderr to a log file, and include a timestamp in each line.