Scheduling Test Runs

Test schedules require a qualifying plan. Check your plan or contact Sales to get started.

Tests can be scheduled to run on frequencies up to every minute. One or more schedules can be configured per test with each schedule using a unique Test-specific or Shared Environment.

Configuring Schedules

To set a schedule, select one of your API tests and then click Schedule. Every schedule requires an environment and frequency. You can create up to 10 schedules per test (maximum recommendation).

The scheduled test runs will begin immediately after saving your changes. For example, if you choose "Every 15 minutes" and save your changes, a test run will begin immediately and then the scheduled test runs will occur every 15 minutes afterwards.

Schedules only affect the scheduled tests BlazeMeter API Monitoring runs on your behalf. You may initiate as many test runs as you like (up to your plan's request limit) via Trigger URLs or manually in the dashboard.

For custom schedules (for instance, at a specific time), use your preferred scheduler (like cron) along with a Trigger URL.

Pausing Scheduled Tests (Creating a Maintenance Window)

You can pause all scheduled test runs temporarily, without modifying or deleting their scheduling logic. This is especially useful for planned maintenance windows, infrastructure changes, or avoiding false alerts during known downtime.

To pause all scheduled tests in your bucket, navigate to Bucket Settings from the dashboard and scroll to Pause Scheduled Tests, then enable or disable the pause toggle.

To pause scheduled tests in selected shared environments only, navigate to Shared Environments. Under your chosen environment settings, select Behaviors and enable or disable the Pause Schedules option.

During a pause, the following behaviors apply:

  • Scheduled tests will be skipped while the pause is active.

  • The underlying schedule is not altered. After unpausing, tests will resume as normal, starting from the next scheduled run.

  • No backlogged or missed tests will be rerun after unpausing.

  • On your Tests list, all paused tests will display a paused indicator, showing that scheduled runs are temporarily disabled.

    The indicator shows whether a test is paused from the bucket () level or the shared environments () level, as shown next:

  • The Schedules tab will also reflect the paused state to help clarify test inactivity.

Other Automation Options

To run your BlazeMeter API tests on every commit or deploy, check out Trigger URLs and CI integrations.