What the expression does
0 0 * * 0 runs every Sunday at midnight. The day-of-week field is 0, and 0 means Sunday in Vixie-style cron.
Only the weekday is restricted. Because day-of-month remains *, each Sunday matches regardless of the date. If you restrict both day-of-month and weekday, the daemon uses OR semantics and the job will run more often than weekly.
When this schedule is useful
- Weekly reports and digest emails.
- Rotating backups or archiving old logs.
- Reindexing search data or refreshing caches that change weekly.
- Reconciling billing or usage records before the new week.
Nearby expressions worth knowing
Small changes to one field produce very different schedules. These variants are the ones people usually want when they search for this cadence:
- Monday at 00:00:
0 0 * * 1— Week starts Monday in most business calendars. - Friday at 18:00:
0 18 * * 5— Weekly close-out before the weekend. - Sunday at 03:00:
0 3 * * 0— After DST transitions, quieter infrastructure. - Twice a week:
0 2 * * 1,4— Monday and Thursday runs.
0 0 * * 1 # Monday at 00:00
0 18 * * 5 # Friday at 18:00
0 3 * * 0 # Sunday at 03:00
0 2 * * 1,4 # Twice a weekTimezone, load and edge cases
Cron evaluates this expression in the timezone of the daemon, not the timezone of the person who wrote it. If the server runs UTC, a schedule that looks like a morning job can fire in the middle of the local night. Select the server timezone in the next-run preview and compare the wall-clock time before deploying.
Some teams think of Monday as the first day of the week; 0 0 * * 1 is Monday, not Sunday.
A Sunday job that fails silently delays the whole week's reports. Send an alert if the expected artifact is missing by a deadline.
DST transitions often happen early Sunday morning in many zones, which is exactly when this schedule fires.
If the schedule runs more often than you expect, check whether day-of-month and day-of-week are both restricted — Vixie cron treats that combination as OR, not AND.
Verify it before shipping
- Run the expression through the explainer and read the English sentence once.
- Check the next five run times in the server's timezone, not your laptop's.
- Execute the command manually with the same user and environment cron will use.
- Redirect stdout and stderr to a log file, and include a timestamp in each line.