Schedules
A schedule runs a regression automatically on a recurring cadence. Every run it creates is a normal execution, attributed to the schedule.
A schedule runs a regression automatically on a repeating cadence: every night at 02:00, every weekday at 09:00, on the 1st of the month. Every run it creates is a normal execution, the same as clicking Run yourself.
Schedules live under Schedules in the sidebar, scoped to a project. A project holds up to 50 schedules, and a regression can have more than one.
Creating a schedule
Click New schedule. The wizard walks three steps: pick the regression, set the cadence, then name the schedule and confirm.
The cadence is a preset (Daily, Weekdays, Weekly, Monthly) with a time of day, or a raw 5-field cron expression under Custom. A monthly schedule set to the 29th or later skips months without that day. Whatever you pick, a schedule fires at most once per day: the cron's minute and hour must each be a single value.
Two more controls apply to every cadence:
- Timezone: the schedule's own IANA timezone. "Every day at 02:00" means 02:00 on the wall clock in that zone, wherever your team or servers are.
- Enable immediately: create the schedule live, or paused so you can enable it later from the list.
Before you confirm, a preview shows the next four runs.
Creating, editing, or deleting a schedule takes the same permission as running tests: Project Admin or Tester on the project, or a Company Admin. Anyone who can view the project can view its schedules. See Members and roles.
When it fires
A fire lands within about 5 minutes of the scheduled time. Read "daily at 02:00" as "daily around 02:00", and use a schedule where the cadence matters, a manual Run where the exact moment does.
The timezone follows daylight saving time, and on the days the clocks change the schedule still fires exactly once.
There is no catch-up. When a schedule was paused, or firing stalled for a while, the next fire is the next future occurrence; missed occurrences are not replayed. Re-enabling a paused schedule plans it from now.
Reading a schedule's status
A schedule shows two signals side by side: a chip about the schedule itself, and a badge for its latest run. The chip appears only when something needs attention.
| Chip | Meaning |
|---|---|
| Disabled | The schedule is turned off and will not fire. |
| Overdue | Firing has stalled: the schedule is well past its planned run time. |
| Invalid | The last fire found the regression invalid, so no run was created. |
| Error | The last fire failed inside Auretis, so no run was created. |
| Skipped | The last fire stood down because a scheduled run of this regression was still active. |
The badge is always present and reflects the latest run the schedule created:
| Badge | Meaning |
|---|---|
| Passed, Failed, Cancelled, Skipped | The final status of the latest run. |
| Running | A run from this schedule is in progress. |
| Fired | The last fire created a run, but that run is no longer available. |
| No runs yet | The schedule has not created a run so far. |
A Failed badge means the run happened and found failing tests, which is the schedule doing its job. It moves on to the next occurrence as planned; Auretis never re-fires a failing regression on its own. Open the run and review the failures.
When a fire creates no run
Three chips mean the last fire produced no execution:
- Skipped: a scheduled run of the regression was still active, from this schedule or from another one targeting it. Scheduled runs of a regression never overlap.
- Invalid: the regression can no longer run, for example a secret it needs was removed or a suite was emptied. The schedule shows the exact reason.
- Error: something went wrong inside Auretis while firing.
In every case the schedule keeps trying on its cadence. Fix the regression and the next fire runs normally; the shown reason clears after the next successful fire.
A run you trigger manually does not block a scheduled fire. The reverse is stricter: while a scheduled run is active, manual runs inside that regression are blocked until it finishes.
Managing schedules
- Pause and resume: toggle a schedule off at any time. A paused schedule shows Disabled, skips its occurrences, and keeps its history.
- Edit: name, cadence, and timezone can change at any time. The regression cannot; create a new schedule to target a different one.
- Delete: the schedule stops firing immediately. Runs it already created keep the schedule's name in their history.
Every run a schedule creates is attributed to it. Run lists show the schedule's name with a calendar icon where a person's name would appear, and the schedule's own page lists its full run history.