On the 15th of every month
Mid-month jobs such as payroll runs or mid-cycle usage reminders.
Checked with the same parser Bex uses to validate schedules. Next run times are computed in your browser.
Cron expression
0 0 15 * *| minute | 0 |
|---|---|
| hour | 0 |
| day of month | 15 |
| month | * |
| day of week | * |
Watch out for
- Days 29–31 do not exist in every month; the 15th is safe, but a schedule for the 31st skips months that are shorter.
- Bex does not set a per-job time zone: the cluster controller's clock decides. Bex's own next-run projection assumes UTC, as shown here.
Next runs
Calculating the next runs…
How to write it
crontab
0 0 15 * * /usr/local/bin/my-job
Kubernetes CronJob
apiVersion: batch/v1
kind: CronJob
metadata:
name: my-job
spec:
schedule: "0 0 15 * *"
concurrencyPolicy: Forbid
jobTemplate:
spec:
template:
spec:
restartPolicy: Never
containers:
- name: my-job
image: my-image
GitHub Actions
on:
schedule:
- cron: "0 0 15 * *"
render.yaml (Bex cron job)
services:
- name: my-cron-job
type: cron
runtime: docker
schedule: "0 0 15 * *"
Related schedules
- On the first day of every month
0 0 1 * * - On the 1st and 15th of every month
0 0 1,15 * *
Run this schedule as a cron job on Bex: declare it in render.yaml and Bex keeps the run history and logs for every execution.
Cron jobs on Bex