Every 6 hours

Four times a day: 00:00, 06:00, 12:00 and 18:00 — a common cadence for data-warehouse loads.

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

Cron expression

0 */6 * * *

minute	0
hour	*/6
day of month	*
month	*
day of week	*

Watch out for

All your six-hourly jobs pile up at the same four moments; offset the minute (17 */6 * * *) if they compete for the database.
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 */6 * * * /usr/local/bin/my-job

Kubernetes CronJob

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

GitHub Actions

on:
  schedule:
    - cron: "0 */6 * * *"

render.yaml (Bex cron job)

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

Related schedules

Every 4 hours 0 */4 * * *
Every 12 hours 0 */12 * * *

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