Every 5 minutes

The default choice for sending queued emails, retrying failed webhooks or checking for new files — frequent, but gentle on databases.

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

Cron expression

*/5 * * * *

minute	*/5
hour	*
day of month	*
month	*
day of week	*

Watch out for

It fires at :00, :05, :10 and so on, not five minutes after you deploy; the first run can come almost immediately or up to five minutes later.
Scheduled runs use Kubernetes Forbid concurrency: a run that would overlap a still-running one is skipped, not queued.
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

*/5 * * * * /usr/local/bin/my-job

Kubernetes CronJob

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

GitHub Actions

on:
  schedule:
    - cron: "*/5 * * * *"

render.yaml (Bex cron job)

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

Related schedules

Every 2 minutes */2 * * * *
Every 10 minutes */10 * * * *
Every 15 minutes */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