Cron expression generator · every hour

Cron job every hour

The crontab line for a job every hour is 0 * * * *. It runs 24 times a day, 8,760 times a year. Edit it below to see the next runs in your time zone.

—

Next runs

    Field by field

    How 0 * * * * reads

    The five fields are minute, hour, day of month, month and day of week. A star means every value.

    FieldValueMeaning
    Minute0minute 00
    Hour*every hour
    Day of month*every day of month
    Month*every month
    Day of week*every day of week

    For example, from Wednesday 6 January 2027 at 10:07 the next runs are: Wed 6 Jan 2027, 11:00; Wed 6 Jan 2027, 12:00; Wed 6 Jan 2027, 13:00; Wed 6 Jan 2027, 14:00; Wed 6 Jan 2027, 15:00.

    When to use it

    What a job every hour is for

    Hourly jobs are the backbone of most servers: log rotation checks, hourly database snapshots, rebuilding aggregates for a dashboard, or renewing tokens that expire.

    Mistakes

    Common mistakes

    • «* * * * *» or «* */1 * * *» runs every minute, not every hour. The minute field must be a fixed number, such as 0.
    • Every job set to «0 * * * *» starts at exactly the same second. Pick another minute, such as «17 * * * *», for jobs that don’t need to run on the hour.
    systemd

    The same schedule as a systemd timer

    On systems with systemd, a timer can replace the crontab line: OnCalendar=hourly. Check it with systemd-analyze calendar "hourly", which prints the next run.

    Monitoring

    Know when it didn’t run

    Cron doesn’t tell you when a job stops running. Add a heartbeat monitor with a period of 1 hour and end the line with a call to its URL, for example 0 * * * * /path/job.sh && curl -fsS -m 10 <ping URL>. If a ping is late by more than the grace time you set, you get an alert, and a call to the URL with /fail reports a failure at once.

    What is the cron expression for a job every hour?

    0 * * * *. It runs 24 times a day, 8,760 times a year, on the server’s clock.

    How do I run a job every hour with systemd instead?

    Create a timer with OnCalendar=hourly next to a service that runs the job, then enable it with systemctl enable --now name.timer. Persistent=true also runs a run that was missed while the machine was off.