Two ways to run a cron job multiple times a day#
There are two distinct approaches, and they suit different needs. The first uses a step value to divide the day into equal intervals. The second uses a comma-separated list to pick exact hours. The right choice depends on whether you need evenly-spaced runs or runs at specific times.
Even intervals — step syntax: run every 6 hours, starting at midnight:
0 */6 * * *
This fires at 00:00, 06:00, 12:00, and 18:00 — four times per day, equally spaced. The */6 means "every 6th hour," and the 0 in the minute field fires at the top of that hour exactly.
Specific times — comma syntax: run at 8 AM, 1 PM, and 7 PM:
0 8,13,19 * * *
Three separate fires, at the hours you specify. No constraints on even spacing. If your job is "send morning, lunch, and evening digests," this is the pattern — the step syntax would give you midnight and 6 AM too, which you don't want.
Common schedules by frequency#
The most common "run N times per day" patterns, all firing at the top of the hour:
0 */12 * * * # twice a day — midnight and noon
0 */8 * * * # three times a day — 00:00, 08:00, 16:00
0 */6 * * * # four times a day — 00:00, 06:00, 12:00, 18:00
0 */4 * * * # six times a day — every 4 hours
0 */3 * * * # eight times a day — every 3 hours
0 */2 * * * # twelve times a day — every 2 hours
For more on a specific interval, see the dedicated guides: every 2 hours, every 6 hours. For sub-hourly schedules, see every 30 minutes, every 15 minutes.
Runs that don't divide 24 evenly#
Step syntax only works cleanly when the interval divides 24 evenly: 1, 2, 3, 4, 6, 8, 12. What happens with */5? The 24-hour clock doesn't divide by 5, so after 24 hours the sequence resets and drifts. */5 fires at hours 0, 5, 10, 15, 20, then resets at the next midnight — 4 runs per day during most day windows, never evenly spaced over a continuous period.
If you need 5 specific runs per day, use a comma list:
0 0,5,10,15,20 * * *
Explicit. Predictable. The five hours you chose, nothing more.
Runs at business hours only#
What if you need a job to run every 2 hours, but only during the workday?
0 8-18/2 * * *
The 8-18/2 syntax means "every 2nd value in the range 8 through 18," so: 08:00, 10:00, 12:00, 14:00, 16:00, 18:00 — six runs. Outside that range, nothing fires. Restrict to weekdays:
0 8-18/2 * * 1-5
Monday through Friday, every 2 hours between 8 AM and 6 PM. For the basics of weekday scheduling, the Monday to Friday guide covers the day-of-week field in detail.
The minute field: easy to get wrong#
When scheduling multiple times per day, the minute field matters more than it looks. A common mistake:
* */6 * * *
This runs every minute during each 6th hour — 60 executions at hours 0, 6, 12, 18. That's 240 runs per day, not 4. The wildcard in the minute position means "every minute of that hour," not "once during that hour." Always specify an exact minute:
0 */6 * * * # correct — once per 6-hour window, at minute 0
30 */6 * * * # fires at :30 past each 6-hour mark
If you want to stagger a job slightly off the top of the hour to avoid resource spikes — many jobs on shared infrastructure hit at :00 — use minute 15 or 45:
15 */4 * * * # every 4 hours, at :15 past the hour
The cron expression builder shows the next five scheduled times as you type — the fastest way to verify your minute field before deploying.
Time zones and multiple daily runs#
A job that runs at 08:00, 12:00, and 18:00 looks clean until daylight saving shifts everything an hour. If your server is on UTC and your users are in a timezone that observes DST, those times will appear to drift twice a year.
Standard crontab has no built-in timezone support. The two practical options: use CRON_TZ at the top of your crontab if your implementation supports it (cronie does, Vixie cron does not), or schedule in UTC and document which local time each expression corresponds to. See the scheduling at a specific time guide for the full timezone breakdown.
Monitor jobs that run multiple times a day#
When a job runs four times per day, a failure at 06:00 might go unnoticed until the 12:00 run — or longer. Cron job monitoring catches each missed run individually. Add a heartbeat ping at the end of your script:
0 */6 * * * /opt/scripts/sync.sh && curl -s https://app.watchcron.app/ping/your-token
WatchCron expects a ping within the grace period after each scheduled run. If the 06:00 ping doesn't arrive by 06:10, an alert fires immediately — before the 12:00 run, before a user notices, before the data gap compounds.
If you'd rather not manage crontab at all, Cloud Cron handles multiple-daily schedules as HTTP triggers with monitoring built in. The same 19 alert channels apply — Slack, PagerDuty, email, Telegram — routed based on how critical each run is. For the broader picture of cron job patterns, the cron jobs overview covers the full expression syntax.
Frequently asked#
Use step syntax for even intervals: 0 */6 * * * fires every 6 hours (4 times per day). Use comma syntax for specific hours: 0 8,12,18 * * * fires at 8 AM, noon, and 6 PM. Always set an exact minute — a wildcard in the minute field runs every minute of each selected hour.
0 */12 * * * runs at midnight and noon. For specific times like 9 AM and 5 PM, use: 0 9,17 * * *. The comma separates multiple hour values.
0 */6 * * * fires every 6 hours: 00:00, 06:00, 12:00, 18:00. To choose specific times instead, use: 0 6,10,14,18 * * *.
The minute field is a wildcard. * */6 * * * fires every minute during each 6th hour — 60 runs per interval. Change it to 0 */6 * * * (or any specific minute) to fire once per interval.
Use a range with a step: 0 8-18/2 * * * fires at 08:00, 10:00, 12:00, 14:00, 16:00, 18:00. Add day-of-week to restrict to weekdays: 0 8-18/2 * * 1-5.