License requirements:
Your team needs an Automation Platform Enterprise license.
Release schedules are only available on team-shared pipelines.
Release schedules let pipeline owners define when releases and release candidates should be promoted, giving teams a consistent weekly cadence.
When you create a release or release candidate, Gearset automatically schedules it for the next available date and time. You can also schedule or reschedule an individual package manually.
Defining your release or release candidate schedule
To set up a release schedule, open your pipeline settings (Settings cog → Edit pipeline settings) and navigate to the Releases tab.
Toggle on Use a release schedule and configure two things:
Days to release - select which days of the week you want to release (Sunday through Saturday). You can pick as many days as you need.
Time to release - choose what time on each of those days the release should be deployed, shown in your local timezone.
The schedule repeats weekly on the selected days and times. You can’t configure a different cadence, such as fortnightly or monthly.
In the example above, the pipeline is configured to release at 9:00 PM on Mondays and Wednesdays. The next scheduled release is shown at the bottom of the panel.
How scheduling works when creating a release or release candidate
When a user creates a new release or release candidate in the pipeline, Gearset automatically schedules the package for the next time in your release schedule. This requires the Create and add to releases permission.
For example, if your schedule is set to Monday and Wednesday at 9:00 PM, and someone creates a release on a Tuesday afternoon, Gearset will schedule the deployment for Wednesday at 9:00 PM.
The scheduled date and time are pre-populated from your release schedule, so there's no manual step to get the timing right.
Schedule an existing release or release candidate
Open Releases or Release candidates in the appropriate pipeline environment.
Select the release from drop down.
Open the dropdown menu and select Schedule deployment.
Choose the deployment date and time.
Save the schedule.
Gearset automatically starts the promotion at the scheduled time.
You can continue adding features before the scheduled deployment. Gearset validates the updated package again after the additional features are merged.
💡 When a release candidate is promoted to the final environment, the resulting release is not automatically scheduled for deployment to Production. This allows time for final checks before choosing a Production deployment time.
How release schedules interact with permissions
Release schedules are enforced differently depending on a user's permissions on the target environment:
| Validate or lower | Run or higher |
Override scheduled deployment time | No - the deployment will always happen at the next scheduled time | Yes - can choose a different time or deploy immediately |
Create a new release or release candidate when another package is already scheduled | No - must wait until the existing scheduled release has been deployed | Yes - can create additional releases regardless |
This gives pipeline owners a way to enforce a consistent release cadence for most of the team, while still giving trusted users the flexibility to deploy outside the schedule when needed.
Why wasn’t my scheduled release or release candidate promoted?
Gearset won’t promote a scheduled package if:
Its validation has failed.
It has merge conflicts with the environment branch.
Its pre-deployment steps are incomplete.
The target environment is blocked.
If the environment is blocked, Gearset postpones the promotion for five minutes and retries when the environment becomes available. If the promotion starts but fails, Gearset displays an error for you to investigate.