Cron every Monday

0 0 * * 1

Runs once a week, at midnight at the start of Monday.

What each field means

FieldPositionMeaning
0minuteonly 0
0houronly 00:00–00:59
*day of monthevery day of month
*monthevery month
1day of weekonly Monday

Example run times

Starting from Wednesday 07 Jan 2026, 10:17, the next runs are:

  • Mon 12 Jan 2026, 00:00
  • Mon 19 Jan 2026, 00:00
  • Mon 26 Jan 2026, 00:00
  • Mon 02 Feb 2026, 00:00
  • Mon 09 Feb 2026, 00:00
  • Mon 16 Feb 2026, 00:00

How often it runs

  • 1 run on each day it is active.
  • Active on 52 of the 365 days in 2026, for 52 runs that year.
  • Runs are always exactly 7 days apart.

Use it on your platform

Linux crontab

0 0 * * 1 /path/to/command

Edit with crontab -e. Cron uses the server's local time zone.

GitHub Actions

on:
  schedule:
    - cron: '0 0 * * 1'

Schedules are evaluated in UTC, and runs can start late when GitHub is busy.

Kubernetes CronJob

apiVersion: batch/v1
kind: CronJob
metadata:
  name: my-job
spec:
  schedule: "0 0 * * 1"
  timeZone: "Etc/UTC"
  jobTemplate:
    spec:
      template:
        spec:
          containers:
            - name: my-job
              image: busybox
              command: ["sh", "-c", "date"]
          restartPolicy: OnFailure

Without timeZone, the schedule follows the time zone of the kube-controller-manager.

AWS EventBridge

cron(0 0 ? * MON *)

AWS uses six fields (the last is the year), needs ? in either day-of-month or day-of-week, and counts weekdays from 1 = Sunday, so names like MON are safer than numbers. EventBridge rules run in UTC; EventBridge Scheduler lets you choose a time zone.

Spring @Scheduled

@Scheduled(cron = "0 0 0 * * 1")

Spring adds a seconds field at the start, so prepend 0 to run at second zero.

Quartz

0 0 0 ? * MON

Quartz also starts with seconds and, like AWS, requires ? in one of the day fields.

Related schedules