Scheduled runs

Each environment can trigger its full selected suite on a recurring schedule. Schedules are configured in the test repository’s .empiricalrun/ENVIRONMENTS.yaml file. They cannot be created or edited in the dashboard.

Configure a schedule

In .empiricalrun/ENVIRONMENTS.yaml, scheduled_trigger can be a cron string:

environments:
  - slug: production
    name: Production
    scheduled_trigger: "0 2 * * *"

Or an object with an explicit concurrency policy:

environments:
  - slug: production
    name: Production
    scheduled_trigger:
      cron: "0 2 * * *"
      concurrency:
        group: production-nightly
        on_conflict: wait

Open a pull request for the change. Empirical does not read the schedule from a feature branch or an open pull request; it is picked up only after the pull request is merged into the test repository’s default branch. Empirical then syncs the file automatically. Settings → Environments → Sync retries the sync or forces Empirical to reread the file from the default branch. Invalid cron syntax or unknown YAML fields cause the sync to fail with a validation message.

Cron format

Empirical accepts standard five-field cron syntax:

minute hour day-of-month month day-of-week

Schedule	Expression
Every four hours	`0 /4 * *`
Every day at 02:00 UTC	`0 2 * * *`
Weekdays at 09:00 UTC	`0 9 * * 1-5`

To pause a schedule, remove scheduled_trigger in a pull request and merge it into the default branch. Disabling an environment also keeps it out of new-run selectors and scheduled execution.

Getting Started

Platform

Features

Integrations

Trigger a test run

Configure a schedule

Cron format

​Configure a schedule

​Cron format

Configure a schedule

Cron format