Scheduled Runs
Configure recurring test runs on a schedule
Schedule tests to run automatically: hourly, daily at a specific time, or weekly on a chosen day.
Creating a monitor
- Open Monitors in the sidebar and click New Monitor.
- Add a scheduled trigger and configure when it fires (details below).
- Enter a monitor name, something like
Checkout flow health check. - Select the target environment.
- Select the test cases to execute.
- Click Create Monitor.
New monitors are enabled right away and run at the next scheduled time.
Configuring the schedule
Each monitor has exactly one scheduled trigger. There are three schedule types:
| Schedule | Options |
|---|---|
| Interval | Every hour, every 3 hours, every 6 hours, or every 12 hours |
| Daily | A specific time of day (HH:MM) in a chosen timezone |
| Weekly | A day of the week plus a time of day, in a chosen timezone |
Daily and weekly schedules use the timezone you pick (it defaults to your local one), so runs fire at the same local time no matter where your team is.
Selecting test cases
The monitor form lists your test suites as an expandable tree. Expand a suite and check the test cases you want. You can take a whole suite, cherry-pick cases across suites, and search by name to find things quickly.
Only published test cases appear in the picker. Depending on your subscription plan, there may be a cap on how many test cases a single monitor can include.
Environment selection
Pick the environment the scheduled runs should target. The agent uses that environment's base URL, the same as in a manual run. Project credentials and assets are available regardless of which environment you pick.
If the project has no credentials, the form shows a warning. Add credentials first if your flows require login.
Managing monitors
- Edit: click the pencil icon in the Monitors table, or open the monitor, to change its name, schedule, test cases, or environment.
- Enable / disable: use the toggle at the top of the edit form. A disabled monitor keeps its configuration but stops triggering runs.
- Delete: click the trash icon in the table and confirm. This removes the monitor, not the runs it already triggered.
Run history
Every execution a monitor triggers lands in Runs alongside manual runs, and the Triggered by column tells you which is which. Open any run to inspect results. Failures send Slack notifications if you've set those up.