Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
layout: src/layouts/Default.astro
pubDate: 2023-01-01
modDate: 2024-08-28
modDate: 2025-08-15
title: Scheduled deployment triggers
icon: fa-solid fa-clock
description: Automatic deployment triggers allow you to define unattended behavior for your project that will cause an automatic deployment of a release into an environment.
Expand All @@ -27,7 +27,8 @@ Scheduled deployment triggers provide a way to configure your projects to create
3. Set the trigger schedule. The options give you control over how frequently the trigger will run and at what time. You can schedule a trigger based on either days of the week, or dates of the month. You can also use a [CRON expression](#cron-expression) to configure when the trigger will run.
4. Select the action the trigger should take when executed.
- **Deploy latest release** re-deploys a release or promote a release between environments. You need to specify the **source environment** and the **destination environment**. The latest successful release in the source environment will be deployed to the destination environment.
- **Deploy new release** deploys a new release which will deployed to the environment you specify in the **destination environment**.
- **Deploy new release** which will create new release and deploy it to the environment you specify in the **destination environment**.
- **Deploy latest release to an environment** deploy the latest release to an environment in the first phase of the selected channel's lifecycle. You need to specify the **destination environment**.

If you are using [channels](/docs/releases/channels) you may also select the channel to use when deploying the release. The latest successful deployment for the specified channel and source environment will be deployed to the same channel and destination environment. If no channel is specified, the latest successful release from any channel and source environment will be selected for deployment.

Expand Down