HTTPfy

Every 45 minutes (not really)

At minute 0 and 45 of every hour: the gaps are 45 minutes, then 15 minutes.

*/45 * * * * Open in Crontab Generator
17,520runs in the next 365 days
336runs per week
15 min / 45 minshortest / longest gap between runs
02:45next run, Wed 11 Nov UTC

What it is used for

Shown because */45 is a frequent mistake. Steps only count within one hour; they do not carry across hour boundaries.

Field by field

FieldValueMatches
Minute*/450, 45
Hour*every value
Day of month*every value
Month*every value
Day of week*every value
 
*/45 * * * * /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
1Wed 2026-11-11 02:45
2Wed 2026-11-11 03:00
3Wed 2026-11-11 03:45
4Wed 2026-11-11 04:00
5Wed 2026-11-11 04:45
6Wed 2026-11-11 05:00
7Wed 2026-11-11 05:45
8Wed 2026-11-11 06:00
9Wed 2026-11-11 06:45
10Wed 2026-11-11 07:00

Things to watch with this schedule

  • Classic cron cannot express a true 45-minute interval. Use a systemd timer with OnUnitActiveSec=45min, a loop with sleep 2700, or schedule every 15 minutes and let the script decide.
  • The minute step /45 does not divide 60: the count restarts at the top of every hour, so the last gap each hour is 15 minutes instead of 45.

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-45-minutes
spec:
  schedule: "*/45 * * * *"
  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: '*/45 * * * *'   # UTC

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

systemd timer

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

[Unit]
Description=Every 45 minutes (not really)

[Timer]
OnCalendar=*-*-* *:00/45: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/45 * * * ? *)

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/45 * * * ?

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