Scheduled checks

An interval schedule adds selected tests to the execution queue. Repeated results help reveal changes and intermittent failures.

Create a schedule

1. Run the tests manually first to verify URLs, authentication, and test data.
2. Open the interval schedule settings and choose a new schedule.
3. Set a name, interval, and test list, then enable it.
4. Check the next run time and the reports produced afterward.

The UI offers 30 minutes, 1 hour, 6 hours, 12 hours, 24 hours, and 1 week. These are repeating intervals, not calendar-based cron expressions such as “every day at 9 AM.”

Schedules store test selections and intervals. There are no separate per-schedule environment or persona fields. Prepare the intended conditions in the project and tests, then verify them in the first scheduled report.

Timing and queue behavior

• A new schedule first becomes due after its configured interval.
• Changing the interval or re-enabling a schedule recalculates the next run from that time.
• When due, tests enter the queue. Other running work can delay their actual start.

Quitting and sleep

The local engine must be running to process schedules. Fully quitting the app, or putting the computer in a state where it cannot execute work, prevents guaranteed execution at the due time.

Missed intervals are not all replayed. After the engine restarts, its next processing tick handles an overdue schedule once and calculates the next interval. This is different from an always-on external monitoring service.

Maintain useful results

Name schedules by purpose. Select tests that can repeat without accumulating unwanted data or conflicting with each other. Account for expired sessions and tests that take longer than the interval.

Review failures and trends in each project's Reports and analytics. With MCP, an external AI can read the latest report and request a permitted investigation. Creating a schedule does not automatically send AI summaries or external notifications.