Skip to main content

On the first day of every month

Monthly invoicing, usage resets and archiving the previous month's records.

Checked with the same parser Bex uses to validate schedules. Next run times are computed in your browser.

Cron expression

0 0 1 * *
minute0
hour0
day of month1
month*
day of week*

Watch out for

  • There is no 'last day of the month' in this cron dialect (L is rejected); schedule the first day and process the previous month instead.
  • 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…

Edit or check this expression in the cron checker

How to write it

crontab

0 0 1 * * /usr/local/bin/my-job

Kubernetes CronJob

apiVersion: batch/v1
kind: CronJob
metadata:
  name: my-job
spec:
  schedule: "0 0 1 * *"
  concurrencyPolicy: Forbid
  jobTemplate:
    spec:
      template:
        spec:
          restartPolicy: Never
          containers:
            - name: my-job
              image: my-image

GitHub Actions

on:
  schedule:
    - cron: "0 0 1 * *"

render.yaml (Bex cron job)

services:
  - name: my-cron-job
    type: cron
    runtime: docker
    schedule: "0 0 1 * *"

Related schedules

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