# Rolling Back a CI Job {% hint style="info" %} For the best experience, set your browser zoom to **80%** in Chrome or Firefox. {% endhint %} The **Rollback** feature enables you to revert a deployment if issues are detected post-deployment or if unintended changes were introduced. *** ### How to Roll Back a Deployment This section explains how to roll back a deployment in your CI jobs. The goal is to restore a previous release or deployment state. *** #### Prerequisites * The **Rollback** checkbox must be selected when creating the CI job. *** #### Steps 1. Navigate to the **CI Job Results** screen. 2. Select the deployment label you want to roll back. 3. Click the **Rollback** icon: ![](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FUevjHyFA6M8y9oRAiTJq%2Fimage.png?alt=media\&token=68128479-7853-446f-87f6-596bd8edbba7)
Rollback Icon Location
4. Under **API Supported > Constructive Changes**, you’ll see the list of metadata components from the original deployment. All are selected by default.
Constructive Changes Selection
Rollback Metadata Overview
5. In **Choose your Pre/Post Destructive Changes**, you can mark metadata present in the destination but absent in the source for deletion. These deletions are logged in the **Rollback Iteration Log**.
Destructive Changes Selection
6. Choose a method for destructive changes: * **Post Destructive Changes**: Deletes components *after* deployment. * **Pre-Destructive Changes**: Deletes components *before* deployment starts. {% hint style="info" %} **Note:** For active **Flow** metadata, you must include the version number. See [FlowDefinition documentation](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_flowdefinition.htm) for details. {% endhint %} 7. The **API Un-Supported** section lists metadata types unsupported by the API. You can manually include these as pre or post-destructive changes.
Unsupported API Components
{% hint style="info" %} **Caution:** Avoid using unsupported API components in rollback, as they may cause rollback failures. {% endhint %} *** ### Additional Deployment Options Available configuration options before rollback: * **Validate Only**: Run a dry-run validation without performing the actual rollback. * **Deploy Purge on Delete**: Permanently deletes components instead of moving them to the Salesforce Recycle Bin. * **Ignore Warnings**: Continues rollback even if warnings are encountered.
Additional Rollback Options
*** ### Apex Test Level Select an **Apex Test Level** to validate your rollback deployment. * For details, see [Apex Unit Tests](https://knowledgebase.autorabit.com/product-guides/arm/arm-features/deployment/apex-unit-tests).
Apex Test Level Selection
*** ### Final Step 9. Click **Rollback** to initiate the process. 10. Once completed, the rollback appears in the **CI Job Results** screen, tagged accordingly. From there, you can: * View rollback reports * Download the rollback package * Re-deploy the rollback if needed