Skip to content

Scheduled Load Tests

Run your load tests automatically on a schedule

Section titled “Run your load tests automatically on a schedule”

Scheduling lets you attach a recurring schedule to a saved load test so LoadFocus runs it for you on an hourly, daily, weekly, or monthly cadence, in the timezone you choose. You get an email only when something needs your attention, so a passing schedule stays quiet.

Scheduling is available on paid Load Testing plans and works for all three engines: cloud load tests, JMeter, and k6.

Open the test you want to schedule from the Load Tests page (use Edit test from the row menu, or open a test you have already saved). On the test page, open More options and click the Run on a schedule row.

Tick Enable recurring schedule to show the schedule fields.

  • Hourly runs the test every hour. Only the minute of the Time of day is used.
  • Every N hours runs it every N hours, with N from 2 to 12, counted from midnight in your timezone (every 6 hours means 00:00, 06:00, 12:00 and 18:00), at the minute you set.
  • Daily runs the test every day at the chosen time.
  • Weekly runs it on the weekdays you tick, at the chosen time.
  • Monthly runs it once a month on the day of month you pick (1 to 28).

New schedules start on Daily. Pick another cadence before you save if you need one.

Set the Time of day (24-hour clock) and the Timezone. The timezone defaults to your browser's timezone, and the next run is always computed in that timezone, so daylight-saving changes are handled for you.

The schedule is saved together with the test, so click Save draft or Run test as you normally do. After Save draft the panel shows "Schedule saved. Next run:" with the date and time. To turn a schedule off, click Remove schedule, or untick the checkbox and save the test.

A scheduled run emails the test owner when it moves into a bad state, in two cases:

  • The run fails its pass/fail thresholds. The email lists which checks failed and links to the results.
  • The run fails to complete (for example it never started or did not finish).

If a test has no pass/fail thresholds set, scheduled runs only alert when a run fails to complete. To get threshold-based alerts, add pass/fail thresholds to the test first.

You get one email when a schedule starts failing, not one for every failing run after it. When a run passes again after a failure, you get a short "resolved" email. Other passing runs send no email.

Scheduled runs count against the same plan limits as your manual runs (parallel test slots and per-day, per-week, per-month, and per-year caps). A scheduled run never exceeds what a manual run on the same team is allowed. When you save the test, the schedule must fit your plan's daily, monthly and yearly caps, together with your team's other enabled schedules of the same test type (cloud, JMeter or k6). A month counts as 31 days and a year as 365, so Daily needs 31 runs a month. A schedule that does not fit is refused with a message such as "This schedule needs N runs per day, but your plan allows M per day." or "Your team's schedules for this test type need N runs per day, but your plan allows M per day."

If a scheduled run cannot start because a limit is reached at that moment, LoadFocus skips that one run and continues with the next scheduled time. The schedule is not paused for a limit collision. What happens next depends on the limit:

  • A plan run cap (daily, weekly, monthly or yearly; your manual runs count toward it too): the schedule panel shows which run was skipped and why, with a message such as "The scheduled run on [date] was skipped: your plan's monthly run limit was reached (manual runs count toward it too).", and the team owner gets an email, at most once per cap in each day, week, month or year. The message goes away once a scheduled run gets past the limits again.
  • A parallel test slot that is still in use, for example by a previous test: the run is skipped silently.

A run that LoadFocus failed to start does not count against your plan's run caps, and neither does a cloud test run that ended without sending a single request (up to two such runs a day). A run you stop yourself always counts.

A schedule is paused, with an email to the owner, only when the account can no longer run it at all, such as a failed payment, a plan that no longer includes scheduling, or repeated errors. After fixing the underlying issue, re-enable the schedule by saving it again.

On the Load Tests page, scheduled tests show a SCHEDULED badge next to the test name, and paused schedules show a SCHEDULE PAUSED badge. Hover the badge to see the cadence and time.

To schedule a test straight from the list, open the row's action menu and choose Schedule test. This takes you to the test page with the Run on a schedule row ready to configure.