> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/deployment/schedule-a-deployment.md).

# Schedule a Deployment

## Scheduled Deployments with Approval Workflow – User Guide

### Overview

The **Scheduled Deployments with Approval Workflow** enhancement in AutoRABIT ARM allows users to schedule deployments for a specific date, time, and time zone.

This feature enables organizations to execute deployments automatically during planned maintenance windows without requiring manual intervention.

For deployments requiring approval, ARM follows the existing **L1/L2 approval workflow**, ensuring that all required approvals are completed before the scheduled deployment executes.

**Availability:** New UI Only\
**Module:** Deployment\
**Feature Flag:** `SCHEDULED_DEPLOYMENTS`

### Key Features

* **Schedule Deployments:** Configure deployments to execute automatically at a selected date, time, and time zone.
* **Approval Workflow Integration:** Supports existing L1/L2 approval processes before deployment execution.
* **Edit Scheduled Deployments:** Modify the scheduled date and time before execution.
* **Cancel Scheduled Deployments:** Cancel pending schedules without deploying changes.
* **Deploy Now:** Execute a scheduled deployment immediately, superseding its existing schedule.
* **Post-Validation Scheduling:** Schedule actual deployments after successful validation.

### How to Schedule a Deployment

1. Log in to AutoRABIT ARM and navigate to **Deployment → Create Deployment**.
2. Configure the deployment source, destination org, and metadata components.
3. Complete the **Deployment Settings** step.
4. Navigate to **Review & Deploy**.
5. Click **Schedule**.
6. Select the required **Date, Time, and Time Zone**.
7. Confirm the schedule.

Once scheduled, the deployment appears in **Deployment History** with the status **Scheduled**.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fqq1D0ECd9SMZZUINilaI%2Fimage.png?alt=media&amp;token=80537cb0-27f2-4e81-a7d5-f49f907f373a" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FLn1OBX2POMj169yrhtqk%2Fimage.png?alt=media&amp;token=1ad44f1b-c743-4d7b-8d50-306f0c5981e8" alt="" width="185"><figcaption></figcaption></figure>

### Scheduling Deployments After Validation

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FJIKGpYL2kTMWTmK50Cuj%2Fimage.png?alt=media&amp;token=7d3b1907-f518-42b8-9c65-edfb7c1d84a6" alt=""><figcaption></figcaption></figure>

ARM also supports scheduling deployments that have already completed validation successfully.

1. Create a deployment and enable **Validate Only**.
2. Submit the deployment for validation.
3. Once validation completes successfully, navigate to **Deployment → History**.
4. Select the validated deployment.
5. Click **Schedule deployment**.
6. Configure the preferred date, time, and time zone.
7. Confirm the schedule.

**Note:** The Schedule option is not available during the initial Validate-Only operation. Users can schedule the actual deployment only after validation completes successfully.

### Approval Workflow for Scheduled Deployments

If the destination Salesforce org requires approval, ARM follows the existing approval workflow.

1. When a deployment is scheduled, ARM initiates the configured approval process.
2. The deployment moves through **L1 Approval Pending** and **L2 Approval Pending**, as applicable.
3. Approvers review and approve the deployment using the existing approval process.
4. Once all required approvals are completed, the deployment remains scheduled until the configured execution time.
5. ARM automatically executes the deployment at the scheduled time.

**Important:** Deployments requiring approval will execute only after all required approvals are completed. If approvals are not completed before the scheduled time, the deployment will not execute automatically.

### Managing Scheduled Deployments

Users can manage scheduled deployments through **Deployment → History**.

#### Edit a Scheduled Deployment

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F0zjVd2gEE3YSryIAZk8r%2Fimage.png?alt=media&amp;token=590b0def-5708-419a-8ec2-827d6f456dcd" alt=""><figcaption></figcaption></figure>

1. Navigate to **Deployment → History**.
2. Select the deployment with the **Scheduled** status.
3. Click **Edit Schedule**.
4. Update the required date and time.
5. Click **Save Schedule**.

The deployment schedule is updated with the new execution time.

*Screenshot 2: Edit Schedule option in Deployment History.*

#### Cancel a Scheduled Deployment

1. Navigate to **Deployment → History**.
2. Select the scheduled deployment.
3. Click **Cancel Schedule**.
4. Confirm the cancellation.

The scheduled execution is cancelled, and the deployment remains available as a draft. No deployment is performed.

#### Deploy Immediately

Users can execute a scheduled deployment immediately by selecting **Deploy Now** from Deployment History.

This action supersedes the existing schedule and initiates the deployment immediately, subject to any applicable approval requirements.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/deployment/schedule-a-deployment.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
