Cron every minute between 9 and 5
At hours 9, 10, 11, 12, 13, 14, 15, 16 and minutes 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59 every Monday, Tuesday, Wednesday, Thursday, Friday.
minute · hour · day of month · month · day of week
What this expression selects
At hours 9, 10, 11, 12, 13, 14, 15, 16 and minutes 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59 every Monday, Tuesday, Wednesday, Thursday, Friday. This is a five-field calendar schedule, interpreted in the timezone you configure. It is not an instruction to wait a fixed duration after the last completion.
Common mistakes
Next five runs in UTC
Computed at build time from . These are examples, not a live clock.
2026-10-19T09:00:00.000Z
2026-10-19T09:01:00.000Z
2026-10-19T09:02:00.000Z
2026-10-19T09:03:00.000Z
2026-10-19T09:04:00.000ZA nearby variation
*/3 * * * *Every 3 minutes. Compare it with the expression above before copying; the selected fields change the calendar times.
Preview live runs in your timezone ↗
Monitor the completed work
Copy a private ping URL from a CronPulse check. Set its schedule to * 9-16 * * MON-FRI in the same timezone as your job runner, and add grace for runtime and scheduling delay. Send success after the work finishes, not when it is enqueued.
Add success and exit-code reporting to crontab. Missing pings are evaluated once a minute; this is not sub-minute monitoring.
Questions
Which time zone does this use?
Does cron wait for the last job to finish?
Related schedules
Give your next job a heartbeat.
20 checks free. No card. Built in Ireland.