Scheduling
Run tests automatically on a cron schedule to catch regressions before your users do.
Scheduled runs let you run tests automatically at regular intervals. Use them to monitor production continuously or to run your test suite on a cadence.
Why schedule?
- Catch regressions early — find out your login test broke before a user reports it
- Monitor production — not just staging. Run tests against your live site to confirm critical paths are working
- No manual effort — tests run while you sleep
Setting a schedule
Open the test
Go to your project, select the test you want to schedule.
Open Schedule settings
Click the Schedule tab on the test page.
Choose a preset
Select how often you want the test to run. See Schedule presets for the available options.
Save
Click Save schedule. The next run fires at the next matching time.
How scheduled runs work
Scheduled runs are triggered by a background worker that reads your schedule configuration and queues a run at the right time. They work exactly like on-demand runs — the same AI agent, the same browser, the same recording and result.
Scheduled runs appear in the Test's run history alongside on-demand runs, labeled with the schedule that triggered them.
Credit usage
Scheduled runs consume credits just like on-demand runs — 1 credit per 10-minute block of agent runtime. If your balance is zero when a scheduled run fires, it is skipped for that interval.
Skipped scheduled runs don't retry. The next run fires at the next scheduled time. Keep an eye on your credit balance if you have high-frequency schedules.
Pausing a schedule
You can pause and resume a schedule at any time from the Schedule tab. Paused schedules don't consume credits.