Schedule recurring tests

Scheduled runs let you treat a test as an always-on regression check. You define a cron expression, pick a timezone, and Maxoperf launches the run on its own.

When to schedule

• Nightly regressions — catch performance drift before standup.
• Hourly probes — small smoke runs to verify availability.
• Weekly load reviews — bigger runs to compare against the prior week.

For ad hoc CI-triggered runs, see Run tests from CI instead.

Create a schedule

1. Open the test and switch to the Schedules tab.

2. Click New schedule.

3. Enter a cron expression. Maxoperf accepts standard 5-field cron syntax. Use the preview to confirm the next few fire times.

4. Pick a timezone so daylight-saving changes do not move your nightly run.

5. Optionally name the schedule — for example, nightly-baseline or hourly-smoke.

6. Save. The schedule starts on the next matching time.

   

   Test detail Schedules tab — each row shows the cron expression, timezone, and next fire time; pause or delete from here.

Cron quick reference

Pattern	Meaning
*/15 * * * *	Every 15 minutes
0 * * * *	Every hour, on the hour
0 2 * * *	Every day at 02:00
0 6 * * 1-5	Weekdays at 06:00
0 0 1 * *	First day of every month at midnight

Pick a quiet time

Schedule heavy regression runs outside business hours so they do not collide with active development work or peak production traffic.

Pause or delete a schedule

From the Schedules tab you can pause a schedule (it stops firing without losing its definition) or delete it entirely. Any runs already in progress when you pause continue to completion.

Where to go next

• Run tests from CI — trigger runs from your build pipeline.
• Build reporting dashboards — track recurring-run results over time.
• Read run results and logs — interpret each scheduled run.