Every quarter
Quarterly reports, key rotation reminders and archiving at the start of each quarter.
Checked with the same parser Bex uses to validate schedules. Next run times are computed in your browser.
Cron expression
0 0 1 1,4,7,10 *| minute | 0 |
|---|---|
| hour | 0 |
| day of month | 1 |
| month | 1,4,7,10 |
| day of week | * |
Watch out for
- The step form
0 0 1 */3 *also works (months 1, 4, 7, 10); the explicit list makes fiscal quarters that start in other months easy to express. - 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 1 1,4,7,10 * /usr/local/bin/my-job
Kubernetes CronJob
apiVersion: batch/v1
kind: CronJob
metadata:
name: my-job
spec:
schedule: "0 0 1 1,4,7,10 *"
concurrencyPolicy: Forbid
jobTemplate:
spec:
template:
spec:
restartPolicy: Never
containers:
- name: my-job
image: my-image
GitHub Actions
on:
schedule:
- cron: "0 0 1 1,4,7,10 *"
render.yaml (Bex cron job)
services:
- name: my-cron-job
type: cron
runtime: docker
schedule: "0 0 1 1,4,7,10 *"
Related schedules
- On the first day of every month
0 0 1 * * - Every 6 months
0 0 1 1,7 *
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