Every Tuesday and Thursday
Twice-weekly jobs such as newsletters, stock reorders or cleanup of stale branches.
Checked with the same parser Bex uses to validate schedules. Next run times are computed in your browser.
Cron expression
0 9 * * 2,4| minute | 0 |
|---|---|
| hour | 9 |
| day of month | * |
| month | * |
| day of week | 2,4 |
Watch out for
- Use a comma for separate days (
2,4); a hyphen (2-4) would include Wednesday. - 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 9 * * 2,4 /usr/local/bin/my-job
Kubernetes CronJob
apiVersion: batch/v1
kind: CronJob
metadata:
name: my-job
spec:
schedule: "0 9 * * 2,4"
concurrencyPolicy: Forbid
jobTemplate:
spec:
template:
spec:
restartPolicy: Never
containers:
- name: my-job
image: my-image
GitHub Actions
on:
schedule:
- cron: "0 9 * * 2,4"
render.yaml (Bex cron job)
services:
- name: my-cron-job
type: cron
runtime: docker
schedule: "0 9 * * 2,4"
Related schedules
- Every Monday at 9 AM
0 9 * * 1 - Every Friday at 5 PM
0 17 * * 5
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