HTTPfy

Every Saturday and Sunday at midnight

At 00:00 on Saturday and on Sunday: 2 runs a week.

0 0 * * 6,0 Open in Crontab Generator
104runs in the next 365 days
2runs per week
1 day / 6 daysshortest / longest gap between runs
00:00next run, Sat 14 Nov UTC

What it is used for

Weekend-only jobs such as heavier analytics batches that would slow systems on working days.

Field by field

FieldValueMatches
Minute00
Hour00
Day of month*every value
Month*every value
Day of week6,0Sunday, Saturday
 
0 0 * * 6,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.

#UTCYour local time
1Sat 2026-11-14 00:00
2Sun 2026-11-15 00:00
3Sat 2026-11-21 00:00
4Sun 2026-11-22 00:00
5Sat 2026-11-28 00:00
6Sun 2026-11-29 00:00
7Sat 2026-12-05 00:00
8Sun 2026-12-06 00:00
9Sat 2026-12-12 00:00
10Sun 2026-12-13 00:00

Things to watch with this schedule

  • 6,0 and 0,6 are equal. A range 6-0 is invalid in cron because ranges cannot wrap; list the days instead or write SAT,SUN.

Kubernetes CronJob

Kubernetes uses the same five fields. 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-weekend-at-midnight
spec:
  schedule: "0 0 * * 6,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.

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

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

systemd timer

The equivalent OnCalendar= value is Sat,Sun *-*-* 00:00:00. Check it with systemd-analyze calendar 'Sat,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 Saturday and Sunday at midnight

[Timer]
OnCalendar=Sat,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 ? * SAT,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 ? * SAT,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