Cron on the 15th of every month

0 0 15 * *

Runs once a month, at midnight on the 15th.

What each field means

FieldPositionMeaning
0minuteonly 0
0houronly 00:00–00:59
15day of monthonly 15
*monthevery month
*day of weekevery day of week

Example run times

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

  • Thu 15 Jan 2026, 00:00
  • Sun 15 Feb 2026, 00:00
  • Sun 15 Mar 2026, 00:00
  • Wed 15 Apr 2026, 00:00
  • Fri 15 May 2026, 00:00
  • Mon 15 Jun 2026, 00:00

How often it runs

  • 1 run on each day it is active.
  • Active on 12 of the 365 days in 2026, for 12 runs that year.
  • The gap between runs varies from 28 days to 31 days.

Use it on your platform

Linux crontab

0 0 15 * * /path/to/command

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

GitHub Actions

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

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 15 * *"
  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 15 * ? *)

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 15 * *")

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

Quartz

0 0 0 15 * ?

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

Related schedules