Home › Quartz › Every hour

At minute 0.

Why use this schedule

One run at the top of each hour, twenty-four a day. This is the classic maintenance cadence: frequent enough to keep data fresh, slow enough that even a heavier job finishes comfortably before the next one starts.

• Rotating or compressing logs
• Hourly aggregation of events
• Refreshing materialised views

First runs, as an example

Starting from 1 January 2027, evaluated in UTC:

Every hour in every dialect

Need to translate a different expression? Use the cron converter.

Ready-to-use Quartz config

Drop this into your project. The expression is the one above.

Trigger trigger = TriggerBuilder.newTrigger()
    .withIdentity("myTrigger", "group1")
    .withSchedule(CronScheduleBuilder.cronSchedule("0 0 * * * ?")
        .inTimeZone(TimeZone.getTimeZone("UTC")))
    .build();

The Quartz fields, in order: second (0-59), minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (1-7, 1 = Sunday), year (1970-2199, optional).

Things to watch out for in Quartz

• Six fields: seconds first, then minute, hour, day-of-month, month, day-of-week. Use 0 in seconds to fire at the start of the minute.
• Quartz uses the JVM default time zone unless you set one: CronScheduleBuilder.cronSchedule(expr).inTimeZone(TimeZone.getTimeZone("UTC")).

The common mistake with this schedule

Many teams start everything at minute 0, which creates a thundering herd on shared systems. Offset heavy jobs, for example to minute 7 or 23, or use H in Jenkins.

Similar Quartz schedules