Schedules

Use a schedule to repeat a saved simulation in the time zone relevant to your application. Run the scenario manually first and check its behavior before making it recurring.

Add a schedule

An owner or admin opens the saved simulation and chooses Schedule. Each simulation has one schedule, which can be changed or paused.

Enter a five-field numeric cron expression and an IANA time zone, such as Europe/London. Check the previewed local times before saving.

Expression	Occurrences
0 9 * * 1-5	At 09:00 Monday through Friday
0 */6 * * *	Every six hours
*/15 * * * *	Every fifteen minutes

Occurrences must be at least fifteen minutes apart, including the gap across an hour boundary. Use a regional time zone rather than a fixed offset or abbreviation so daylight-saving behavior is explicit.

Change or pause the schedule

Pause the schedule to keep its rule without launching new runs. This does not stop an active run; use Stop on the run itself.

Edits to the simulation definition apply to subsequent scheduled launches. Earlier runs retain their own definition snapshots.

Account for skipped occurrences

A scheduled occurrence is skipped while a previous run of the same definition may still be active or releasing resources. It is not queued for later. Manual launches are not subject to this schedule-overlap rule.

An occurrence more than five minutes late is also skipped rather than replayed after an outage. Check the schedule’s errors and skipped occurrences when an expected run is absent.

Daylight-saving transitions follow the chosen region: a nonexistent local time is skipped, while a repeated local time can occur twice. Choose a schedule outside the transition period if that distinction matters to the test.