Cron schedule reference

Cron leap day

At 00:00 on day 29 of the month in FEB.

0 0 29 FEB *

minute · hour · day of month · month · day of week

What this expression selects

At 00:00 on day 29 of the month in FEB. 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

February 29 only occurs in leap years. This engine searches up to eight years; February 30 has no valid occurrence and is rejected.

Next five runs in UTC

Computed at build time from 19 Oct 2026, 00:00 UTC. These are examples, not a live clock.

2028-02-29T00:00:00.000Z
2032-02-29T00:00:00.000Z
2036-02-29T00:00:00.000Z
2040-02-29T00:00:00.000Z
2044-02-29T00:00:00.000Z

A nearby variation

*/5 9-16 * * MON-FRI

At hours 9, 10, 11, 12, 13, 14, 15, 16 and minutes 0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55 every Monday, Tuesday, Wednesday, Thursday, Friday. 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 0 0 29 FEB * 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?

The examples use UTC. Choose your IANA time zone in the cron helper; your host scheduler must use the same zone.

Does cron wait for the last job to finish?

This expression chooses clock times. It does not provide locking or an elapsed timer. Configure concurrency in the job runner.

Related schedules

Cron every five minutes business hours

Cron every minute

One URL. A little more peace of mind.

Give your next job a heartbeat.

20 checks free. No card. Built in Ireland.

Create your first check ↗