Skip to main content
bex.co
419

Every minute

Polling a queue or health endpoint as often as cron allows; cron has no seconds field, so once a minute is the fastest schedule.

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

Cron expression

* * * * *
minute*
hour*
day of month*
month*
day of week*

Watch out for

  • A job that takes longer than a minute overlaps the next run. On Bex the overlapping scheduled run is skipped, so a slow job silently runs less often than you expect.
  • GitHub Actions does not run scheduled workflows more often than every 5 minutes, and delays them under load; use crontab or a Bex cron job for tighter schedules.
  • 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

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

Kubernetes CronJob

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

GitHub Actions

on:
  schedule:
    - cron: "* * * * *"

render.yaml (Bex cron job)

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

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