What the expression does
0 * * * * runs the command at minute 0 of every hour: 00:00, 01:00, 02:00 and so on, 24 times per day.
Only the minute field is fixed (0). The hour field is a wildcard, so every hour matches. If you write * * * * * instead, the job runs every minute, not every hour.
When this schedule is useful
- Recalculating hourly aggregates from event data.
- Rotating logs or cleaning temporary files that accumulate quickly.
- Polling an upstream system that updates once per hour.
- Sending an hourly heartbeat or status digest.
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:
- Hourly at :15:
15 * * * *— Avoids the top-of-hour spike. - Every 2 hours:
0 */2 * * *— Fires at 00:00, 02:00, 04:00… - Hourly, business hours:
0 9-17 * * 1-5— Nine runs per weekday. - Every 30 minutes:
*/30 * * * *— Twice per hour at :00 and :30.
15 * * * * # Hourly at :15
0 */2 * * * # Every 2 hours
0 9-17 * * 1-5 # Hourly, business hours
*/30 * * * * # Every 30 minutesTimezone, 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.
Everyone schedules at minute 0, so shared infrastructure sees a spike at the top of the hour. Offset to minute 7 or 12 to spread load.
A job that takes 61 minutes silently overlaps the next hour. Use a lock or reduce the run time.
During a DST fall-back, the 01:00 hour can occur twice; an hourly job may run 25 times that day.
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.