Schedules
One-shot and recurring schedules, timezones, launch retries, and next-run behavior.
A Schedule automation runs once at a future time or repeats on a cron cadence.
Run once
Choose Run once in the Schedule field and enter a future date and time in your browser's timezone. The automation becomes eligible at that instant and starts on an eligible scheduler tick.
One-shot schedules support the same launch retries as recurring schedules. Pause or delete the automation to cancel pending starts, including retries. To resume a one-shot whose scheduled time has passed, choose a new future time first.
Schedule mode is fixed after creation. You can edit a one-shot's time, but cannot convert it to a recurring schedule.
Recurring presets
The recurring schedule picker offers four presets and a custom mode. Every preset builds a standard cron expression for you.
| Preset | Runs | Controls |
|---|---|---|
| Every hour | Once per hour at the top of the hour | None |
| Daily | Once per day at the chosen hour | Hour picker (12-hour, AM/PM) |
| Weekly | Once per week on the chosen day and hour | Day of week (Monday to Sunday) and hour picker |
| Monthly | Once per month on the chosen day and hour | Day of month (1st to 28th) and hour picker |
| Custom | Any valid 5-field cron expression | Text input with live validation |
Below the controls the picker shows a plain-language description of the schedule and a Next run preview computed in the selected timezone. A new schedule automation defaults to 0 9 * * * (daily at 9:00 AM).
Custom cron expressions
Custom expressions use the standard five fields:
minute hour day-of-month month day-of-week| Expression | Meaning |
|---|---|
*/15 * * * * | Every 15 minutes |
0 9 * * * | Daily at 9:00 AM |
30 14 * * 1-5 | Weekdays at 2:30 PM |
0 9 * * 1 | Mondays at 9:00 AM |
0 0 1 * * | First of every month at midnight |
Rules enforced when you save:
- 15-minute minimum. Expressions that fire more often than every 15 minutes, such as
*/5 * * * *, are rejected with "Schedule interval must be at least 15 minutes". The check looks at the shortest gap between consecutive firings, so0,1 * * * *is rejected too. - Five fields only. Six-field expressions with a seconds column are not supported. The picker shows "Invalid cron expression. Use 5-field format (minute hour day month weekday)."
- The Create Automation and Save Changes buttons stay disabled while the expression is invalid.
Timezone
The Timezone field defaults to your browser's timezone when you create an automation. A "Common" group lists UTC and a dozen major zones; "All Timezones" lists every IANA zone and is searchable. The schedule is evaluated in this zone, so "9:00" means 9:00 local time there, including across daylight-saving changes.
Next-run recalculation

- Saving a change to a recurring schedule or its timezone recalculates the next run automatically.
- Resume on a paused recurring automation computes the next run from the current moment rather than catching up on missed slots. A one-shot resumes at its configured future time.
- A schedule slot that comes due while a previous run is still active is skipped (see below). A recurring schedule advances to the following slot; a one-shot consumes that slot.
- Execution authorization denial records a Skipped invocation and immediately pauses the automation, clearing the next run time without adding a failure strike. Restore the required executor/team/target access or reassign the executor, then click Resume; restoring access or reassigning alone does not restart the schedule.
Trigger Now
Trigger Now on the detail page starts a one-off run immediately across the automation's full repository and environment selection.
- It does not move the next scheduled run; the cron cadence stays fixed.
- It is rejected with "A run is already active for this automation" when a run is in progress. Nothing is recorded for the rejected attempt.
- It works while the automation is paused, so you can verify a fix before resuming. A successful manual run resets the consecutive-failure counter without resuming the automation; a failed one counts toward auto-pause like any other run.
- It runs under the authority and identity of the person who clicked it, not the stored executor used by scheduled runs.
- For a team automation, the requester must currently belong to its active owning team, including Administrators and Owners. Session-creation and target-use permissions and current team repository grants are checked at execution time. Editing or reading the automation is not enough to run it.
Both scheduled and manual runs keep the automation's team ownership and use the team's default session visibility at launch. See Ownership and execution for access rules and API-only executor reassignment.
One active run at a time
For scheduled and manual firings, only one run per automation can be active. A run waiting to retry counts as active. When the schedule comes due during an active run, the firing is recorded in Run History as Skipped with the note "Skipped because a previous run is still active". Skipped firings never count toward auto-pause.
Event-driven triggers use per-event concurrency keys instead; see each trigger's page.
Retries
A transient outage can stop a scheduled run from starting, for example when its session cannot be created. Set Retries (none by default, up to 5) to launch such a run again instead of failing it. This applies to both recurring and one-shot schedules:
- Only a run that failed before its instructions reached a session is retried. A run that fails after it starts, a run whose configuration can't run (for example a model its harness doesn't support), and a Trigger Now run fail as usual.
- The first retry waits 2 minutes, and the wait doubles for each later attempt. Meanwhile the row shows Retrying with the launch error and the time of the next attempt.
- Each attempt opens a new session under the same run row, which shows the attempt number once the run has relaunched. Access is checked again before each attempt, as at the original firing.
- A run that relaunches successfully counts as a success. A run that uses up its retries fails with its last error and counts as one failure toward auto-pause. When another target of the same firing fails, that failure counts once the waiting run finishes, so it can't pause the automation out from under the retry.
- Pausing or deleting the automation, or lowering its retries below the attempts a waiting run has made, prevents that run from relaunching. The scheduler marks it Failed during its once-per-minute retry sweeps. Sweeps process a limited batch, so a backlog can delay the status change across multiple sweeps.
- A one-shot consumes its scheduled time when its invocation is admitted. Retries reuse that invocation and run; they do not schedule another firing. The automation stays enabled while its runs are active or waiting to retry, then disables once they finish.
- Rescheduling a one-shot withdraws waiting retries for its previous scheduled time. A future schedule remains eligible to run.
Multi-repository schedules
Schedule triggers are the only trigger type that accepts more than one target. Select up to 10 repositories and environments combined, and every firing fans out into one session per target, all launched concurrently. See Multi-repository automations.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| "Schedule interval must be at least 15 minutes" | The expression fires more often than every 15 minutes, or its shortest gap is under 15 minutes | Use */15 or a slower cadence |
| The expression is rejected as invalid | It has six fields (seconds) or a syntax error | Use five fields; the placeholder 0 9 * * 1-5 shows the format |
| The next run is not when you expected | The timezone is set to a different zone than you assumed | Check the Timezone field; the Next run preview shows the resolved time |
| A firing shows as Skipped but the schedule remains enabled | The previous run was still active when the slot came due | Shorten the work per run, lengthen the interval, or check whether the earlier run is stuck via View session |
| A firing shows as Skipped and the automation pauses immediately | Execution authorization was denied | Restore the required access or reassign the executor, then click Resume |
Next steps
Create your first automation
Build a weekly scheduled automation that opens a dependency-update pull request, test it with Trigger Now, and read its run history.
Inbound webhooks
Trigger an automation from any system with an authenticated JSON POST, filter payloads with JSONPath conditions, and deduplicate retries.