Schedule

Automations > Schedule holds everything set to run in the organization, from every group: one-time scheduled runs and recurring runs. The schedule also shows what has already run, with the result, and what should have run but didn't.

The Schedule requires a plan with scheduled or recurring runs. Times are shown in your profile's time zone.

Indicators

Indicator	What it counts
Today	Today's rounds and how many have already run.
Next 24 hours	What is set to run in the next 24 hours, with the next round.
Active recurring runs	How many recurring runs are active, and how many are paused.
Last 7 days	What didn't run and what failed in the last week.

Views

View	What it's for
Week	The week as an hourly grid, with a line marking the current time. Click an empty slot to schedule there.
Month	The whole month. An alert icon marks a day with a failure or with something that didn't run.
List	From yesterday through the next 14 days, as a list. It is the default view on a phone.
By runner, in the day	A 24-hour strip per runner or cluster, to spot overlaps and free slots.

The filters pick the group, the runner or cluster, and the type (scheduled or recurring runs), and show or hide paused recurring runs and cancelled items. Very frequent recurring runs (every few minutes or hours) are summarized per day, as "N times".

What each item shows

Status	When
Scheduled	It will run, or it is waiting for the runner.
Running now	There are runs in progress.
Passed	No run failed.
Failed	No run passed.
With failures	Some passed and some failed, with the count (for example, 34/38).
Did not run	The batch never got to run. The reason appears on the item.
Paused	The recurring run is paused, by a person or by Proton.
Skipped	This occurrence of the recurring run was skipped.
Cancelled	The batch was cancelled. It only appears with the cancelled filter.

Why something didn't run

• The runner was down at the scheduled time and didn't come back within 1 hour.
• More than 1 hour passed after the scheduled time and the batch didn't go out.
• The runner or cluster no longer exists.
• The cycle or group was closed.
• The scheduled run's datasets no longer exist.
• The person who scheduled it is no longer active in the organization.
• The organization's plan no longer includes the feature.

Schedule a run

Schedule (or a click on an empty slot in the week) opens a five-step wizard:

1. What to schedule: the automation group. The runs land in the group's open cycle (if more than one cycle is open, choose the cycle). Only groups with an open cycle are listed. New group opens the Automation Center in another tab; when you come back, the new group is already selected.
2. What will run: the group's automations. You can adjust the parameters, by dataset or by parameter.
3. Where it runs: the runner or the cluster. For a mobile automation, also the device and the app. You can schedule on a runner that is offline: it just needs to be online at the scheduled time.
4. When: Schedule, with the date and time, or Recurring, with the frequency.
5. Code and environment: the branch for each system (the default one is already selected), the environment, and the options to get a notification and to re-run on failure.

Ask the AI

With the AI module, the first step offers Rather describe it? Ask the AI: write what to run and when, such as "Monday to Friday at 07:00, run the Regression group". The wizard finds the automations and the runner, shows the summary, and only schedules after you approve. It uses AI credits.

Recurring runs

Frequency	How it works
Minute	Every N minutes (1 to 59), counting from the previous round.
Hour	Every N hours (1 to 23), counting from the previous round.
Daily	Every day, at the chosen time.
Weekly	On the chosen days (with shortcuts for weekdays and weekends), at the chosen time.
Monthly	On a day of the month or on the last day of the month. A month that doesn't have the chosen day (such as the 31st) is skipped.

• The rule follows the time zone of the person who created the recurring run. Changing the profile's time zone later doesn't shift what has already been scheduled.
• Each round uses the branch and the environment chosen in the recurring run.
• If the previous round is still in progress, or waiting for the runner, the current round is skipped.
• Nothing is retroactive: a missed round (for example, more than 1 hour late) doesn't run later.

Automatic pause

Proton pauses the recurring run when it can no longer run: the plan no longer includes recurring runs, the person who created it left the organization, the cycle or group was closed, or the runner or cluster was removed. Fix the cause and use Resume.

A recurring run created by someone who left the organization won't run again: create a new one.

The runner at the scheduled time

If the runner is offline at the scheduled time, the batch waits. If the runner comes back within 1 hour, the run starts late; otherwise, the batch is marked Did not run. On a cluster, it's enough for one runner in the cluster to be online.

Actions for each item

Clicking an item opens its details: when, the expected duration, where it runs, who created it, the rule (for a recurring run), the automations, the next times, and the last rounds.

Action	Where	What it does
Run now	Recurring or scheduled run	Runs once now, without changing the recurring run's rule.
Reschedule	Scheduled run that hasn't gone out yet	Changes the date and time.
Pause and Resume	Recurring run	Stops it and makes it run again.
Edit	Recurring run	The frequency, the runner, the branches, the automations, the environment, and the options.
Skip this time	A future occurrence of the recurring run	Skips only this occurrence; Undo skip then appears.
Cancel this time	Recurring run batch that hasn't gone out yet	Cancels only this batch.
Delete recurring run	Recurring run	The next occurrences leave the schedule; what already ran stays in the history.
Delete scheduled run	Scheduled run that hasn't gone out yet	The scheduled run leaves the schedule and doesn't run.
Open the group in the Automation Center	Any item	Opens the group and the cycle.

When an item's runner or cluster has been removed, the details warn you: edit the recurring run and choose another runner, or delete the scheduled run and schedule it again.

Permissions

Viewing the Schedule requires viewing the Automation Center; scheduling and using the actions require run permission in the Automation Center. Scheduling requires the scheduling feature in the plan, and creating a recurring run requires the recurring run feature.