HTTPfy

Every Tuesday and Thursday at 9am

At 09:00 on Tuesday and Thursday: 2 runs a week.

0 9 * * 2,4 Open in Crontab Generator
105runs in the next 365 days
2runs per week
2 days / 5 daysshortest / longest gap between runs
09:00next run, Thu 12 Nov UTC

What it is used for

Twice-weekly reminders, reports and syncs.

Field by field

FieldValueMatches
Minute00
Hour99
Day of month*every value
Month*every value
Day of week2,4Tuesday, Thursday
 
0 9 * * 2,4 /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
1Thu 2026-11-12 09:00
2Tue 2026-11-17 09:00
3Thu 2026-11-19 09:00
4Tue 2026-11-24 09:00
5Thu 2026-11-26 09:00
6Tue 2026-12-01 09:00
7Thu 2026-12-03 09:00
8Tue 2026-12-08 09:00
9Thu 2026-12-10 09:00
10Tue 2026-12-15 09:00

Things to watch with this schedule

  • Gaps are 2 days and then 5 days.

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-tuesday-and-thursday
spec:
  schedule: "0 9 * * 2,4"
  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 9 * * 2,4'   # UTC

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

systemd timer

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

[Unit]
Description=Every Tuesday and Thursday at 9am

[Timer]
OnCalendar=Tue,Thu *-*-* 09: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 9 ? * TUE,THU *)

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 9 ? * TUE,THU

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