Cron every Sunday at midnight (0 0 * * 0): next runs and syntax

What it is used for

This is what @weekly means in cron: weekly backups, log archiving, full re-indexes and certificate renewal checks.

Field by field

Field	Value	Matches
Minute	`0`	0
Hour	`0`	0
Day of month	`*`	every value
Month	`*`	every value
Day of week	`0`	Sunday

0 0 * * 0 /path/to/job

Next 10 run times

Computed when this page loaded (2026-11-11 02:24 UTC), assuming the scheduler runs in UTC.

#	UTC	Your local time
1	`Sun 2026-11-15 00:00`	-
2	`Sun 2026-11-22 00:00`	-
3	`Sun 2026-11-29 00:00`	-
4	`Sun 2026-12-06 00:00`	-
5	`Sun 2026-12-13 00:00`	-
6	`Sun 2026-12-20 00:00`	-
7	`Sun 2026-12-27 00:00`	-
8	`Sun 2027-01-03 00:00`	-
9	`Sun 2027-01-10 00:00`	-
10	`Sun 2027-01-17 00:00`	-

Things to watch with this schedule

Midnight on Sunday is the boundary between Saturday night and Sunday. If you mean the night between Sunday and Monday, use 0 0 * * 1.
systemd's shorthand OnCalendar=weekly is Monday 00:00, not Sunday. Moving a @weekly job from cron to a systemd timer with weekly shifts it by a day.

Kubernetes CronJob

Kubernetes uses the same five fields and also accepts @weekly. Set spec.timeZone (stable since Kubernetes 1.27), otherwise the schedule follows the time zone of kube-controller-manager.

apiVersion: batch/v1
kind: CronJob
metadata:
  name: every-sunday-at-midnight
spec:
  schedule: "0 0 * * 0"
  timeZone: "Etc/UTC"
  concurrencyPolicy: Forbid
  startingDeadlineSeconds: 300
  jobTemplate:
    spec:
      template:
        spec:
          restartPolicy: OnFailure
          containers:
            - name: job
              image: debian:bookworm-slim
              command: ["/bin/sh", "-c", "/app/run-job.sh"]

GitHub Actions

Workflow schedules use five-field cron in UTC and run only from the default branch. Runs at minute 0 are the most likely to be delayed or dropped when GitHub is busy; an odd minute such as 7 or 23 starts more reliably. The @weekly shorthand is not accepted there.

on:
  schedule:
    - cron: '0 0 * * 0'   # UTC

jobs:
  run:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: ./run-job.sh

systemd timer

The equivalent OnCalendar= value is Sun *-*-* 00:00:00. Check it with systemd-analyze calendar 'Sun *-*-* 00:00:00', which prints the next elapse time. Persistent=true runs a missed job after downtime, which classic cron never does.

[Unit]
Description=Every Sunday at midnight

[Timer]
OnCalendar=Sun *-*-* 00:00:00
Persistent=true

[Install]
WantedBy=timers.target

AWS EventBridge

EventBridge rules take six fields (minute, hour, day-of-month, month, day-of-week, year) in UTC; EventBridge Scheduler can use a time zone. One of day-of-month and day-of-week must be ?, and day-of-week runs 1-7 from Sunday, so names are used here.

cron(0 0 ? * SUN *)

Quartz Scheduler (Java)

Quartz adds a leading seconds field and needs ? in either day field; days of the week are 1 (SUN) to 7 (SAT).

0 0 0 ? * SUN

Spring's @Scheduled(cron = ...) also uses six fields, but numbers days of the week 0-7 with Sunday as 0 or 7, like Unix cron; the names shown above work in both.

Related schedules

Every Monday at 9am 0 9 * * 1
Every weekday at 9am 0 9 * * 1-5
Every weekday at midnight 0 0 * * 1-5
Every Friday at 5pm 0 17 * * 5
Every Saturday at midnight 0 0 * * 6
Every Monday at midnight 0 0 * * 1
All cron schedules and the field reference
Build a crontab line from this schedule