{"id":3590,"date":"2026-07-04T11:53:16","date_gmt":"2026-07-04T11:53:16","guid":{"rendered":"https:\/\/loadfocus.com\/blog\/?p=3590"},"modified":"2026-07-04T11:54:39","modified_gmt":"2026-07-04T11:54:39","slug":"scheduled-load-tests","status":"publish","type":"post","link":"https:\/\/loadfocus.com\/blog\/2026\/07\/scheduled-load-tests","title":{"rendered":"Schedule recurring load tests, and get alerted only when performance breaks"},"content":{"rendered":"<\/span> 5<\/span> minutes read<\/span><\/span>\n

Performance rarely breaks on the day you run a load test. It breaks three deploys later, on a Tuesday, when nobody is looking. LoadFocus can now run your load tests for you on a recurring schedule, and email you only when a run actually starts failing. Set it once, and let it watch your app.<\/p>\n\n\n\n

Most teams run a load test right before a big launch, see green, and move on. Then the code keeps changing: a new query here, an extra API call there, a caching change that looked harmless in review. By the time someone runs the next manual test, the regression has already shipped. Scheduled load tests close that gap. You attach a schedule to a test you have already saved, pick how often it should run, set your pass and fail thresholds, and LoadFocus takes it from there.<\/p>\n\n\n\n

Pick how often your test runs<\/h2>\n\n\n\n

You are no longer limited to a single cadence. A scheduled load test can run on any of these frequencies, in the time and timezone you choose:<\/p>\n\n\n\n

Hourly for critical paths you never want to regress<\/p>\n\n\n\n

Every few hours from every 2 up to every 12<\/p>\n\n\n\n

Daily the classic overnight smoke test<\/p>\n\n\n\n

Chosen weekdays for example Mon, Wed and Fri<\/p>\n\n\n\n

Weekly on the day and time you pick<\/p>\n\n\n\n

Monthly for slower moving systems<\/p>\n\n\n\n

Higher frequencies are checked against your plan’s daily run limit before the schedule is saved, so you never set up something your plan cannot actually run. If a cadence would exceed your limit, LoadFocus tells you up front instead of silently skipping runs later.<\/p>\n\n\n\n

Alerts only when it matters<\/h2>\n\n\n\n

A monitor that emails you after every run trains you to ignore it. Scheduled load tests do the opposite. The alerting is transition based, which means you hear about the change<\/em>, not the routine:<\/p>\n\n\n\n

\"Passing
You get an email when a run starts failing, a follow up when it recovers, and nothing while it keeps passing.<\/figcaption><\/figure>\n\n\n\n