Run 1
Jun 28, 2026, 00:00:00 GMT
Cron preset
Every Sunday at midnight cron
0 0 * * 0 means runs every sunday at 00:00.
Meaning
At 00:00, only on Sunday
Run 1 · Asia/Shanghai
Jun 28, 2026, 00:00:00 GMT+8
2026-06-27T16:00:00.000Z
Run 2 · Asia/Shanghai
Jul 05, 2026, 00:00:00 GMT+8
2026-07-04T16:00:00.000Z
Run 3 · Asia/Shanghai
Jul 12, 2026, 00:00:00 GMT+8
2026-07-11T16:00:00.000Z
Run 4 · Asia/Shanghai
Jul 19, 2026, 00:00:00 GMT+8
2026-07-18T16:00:00.000Z
Run 5 · Asia/Shanghai
Jul 26, 2026, 00:00:00 GMT+8
2026-07-25T16:00:00.000Z
Upcoming UTC examples
Run 2
Jul 05, 2026, 00:00:00 GMT
Run 3
Jul 12, 2026, 00:00:00 GMT
Run 4
Jul 19, 2026, 00:00:00 GMT
Run 5
Jul 26, 2026, 00:00:00 GMT
How to use it
Good for weekly maintenance windows and low-traffic batch processing.
Use 0 0 * * 6 for Saturday midnight instead.
Always confirm the scheduler time zone. A daily or weekly cron can move relative to UTC when the local zone enters or leaves daylight saving time.
Frequently asked questions
What cron expression means every sunday at midnight?
Use 0 0 * * 0. Runs every Sunday at 00:00.
Which time zone does this cron use?
The scheduler decides the time zone. Preview the expression in TimeKit with the same IANA time zone your server or job runner uses.
Can daylight saving time affect this schedule?
Yes. Schedules tied to local hours can shift relative to UTC when the selected zone enters or leaves daylight saving time.