> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/use-gitops/application/rollback-gitops-applications.md).
# Rollback GitOps applications
Harness GitOps supports the same rollback operation as Argo CD (`argocd app rollback`). You can restore a previous deployment revision from the application **History & Rollback** tab, automate the same action with a **GitOps Rollback** pipeline step, or trigger a post-production rollback from the **Services** dashboard after a successful deployment.
***
### What will you learn in this topic?
* How to [trigger a post-production rollback](#post-production-rollback-from-the-services-dashboard) from the Services dashboard after a successful deployment.
* How to [manually roll back](#roll-back-from-the-history-and-rollback-tab) a GitOps application to a previous revision from the History and Rollback tab.
* How to [automate rollback](#roll-back-with-the-gitops-rollback-step) with the GitOps Rollback pipeline step.
* How [revisions work](#how-revisions-work) and what settings affect rollback availability.
***
### Before you begin
* **GitOps Application:** Create and sync a GitOps Application that has at least one previous deployment revision. Go to [Add a Harness GitOps Application](/continuous-delivery/use-gitops/get-started/harness-cd-git-ops-quickstart.md#step-4-add-a-harness-gitops-application) to create one.
* **Deployment history:** Rollback is available only for previous revisions. The current revision does not show a 'Rollback' action.
* **Successful pipeline deployment (post-production rollback only):** The **Rollback** button only appears for GitOps applications that were successfully deployed through a pipeline. Failed or in-progress deployments do not show the button.
* **Rollback steps configured (post-production rollback only):** Your pipeline must have rollback steps defined in the **Rollback** tab of the deployment stage. If no rollback steps are configured, the button still appears but the rollback execution will have no steps to run.
* **Pipeline access (post-production rollback only):** You need Execute permission on the pipeline that was used for the original deployment.
* **Pipeline stage (pipeline step only):** Use a deployment stage with GitOps enabled when you add the GitOps Rollback step.
***
### How revisions work
```yaml
- step:
type: GitOpsRollback
spec:
revisionsToRollback: 1 # 1 = one sync ago, not one commit ago
# check available revisions: app > History & Rollback tab
applicationsList:
- agentId: my-agent
applicationName: payments-api
historyId: 7 # pin to an exact revision ID
# find the ID: History & Rollback tab > revision card
# same commit SHA can appear under multiple IDs when
# Helm values differ between syncs — ID is the version
# key, not the SHA
```
```yaml
# Argo CD Application manifest — two settings that affect rollback availability
spec:
revisionHistoryLimit: 10 # default — entries beyond this are evicted permanently
# increase before you need a deeper rollback window
# check/edit: app > App Details tab > spec.revisionHistoryLimit
syncPolicy:
automated: {} # rollback blocked while set
# disable auto-sync first or the step fails with FailedPrecondition
```
{% hint style="info" %}
Rollback does not touch Git or `spec.source`. The app shows OutOfSync after rollback — that is expected. New revisions are recorded on sync only, not on spec edits.
{% endhint %}
{% hint style="warning" %}
**DYNAMIC VALUES RE-RESOLVE AT ROLLBACK TIME**
Harness expressions, Vault refs, and external secrets re-resolve with their current values when the rollback runs. The source snapshot is identical to the original deploy but rendered manifests may differ.
{% endhint %}
***
### Roll back from the History and Rollback tab
1. In your GitOps project, go to **Deployments** > **GitOps** > **Applications**, and then select your application.
2. Select the **History & Rollback** tab.
3. Review the deployment history. Each card shows the revision number, deploy time, how long the revision was active, and who initiated the deploy.
4. On the revision you want to restore, select 'Rollback'.
The current revision is marked with a **Current** badge and does not include a 'Rollback' button.
***
### Roll back with the GitOps Rollback step
1. Select a pipeline and open the **Execution** tab of a GitOps-enabled deploy stage.
2. Select 'Add Step', and then select 'GitOps Rollback'.
3. Configure the step parameters (see [reference](#step-parameter-reference) below).
4. Select 'Apply Changes'.
5. Save and run the pipeline.
***
### Step parameter reference
```yaml
- step:
type: GitOpsRollback
name: GitOpsRollback
identifier: GitOpsRollback
spec:
revisionsToRollback: 1 # step-level fallback, applied to any app with no historyId
# or per-app revisionsToRollback — default: 1
prune: false # prune resources absent from the rolled-back revision
waitTillHealthy: true # hold step until app reaches Healthy — default: false
failOnTimeout: false # when waitTillHealthy: true, fail if Healthy not reached
# before timeout — default: false
applicationsList:
- applicationName: my-app
agentId: my-agent
historyId: 17 # highest precedence — rolls back to this exact entry
- applicationName: another-app
agentId: my-agent
revisionsToRollback: 2 # per-app override — overrides step-level revisionsToRollback
- applicationName: third-app
agentId: my-agent # no historyId or per-app override — inherits step-level: 1
timeout: 10m
```
#### Top-level parameters
| Parameter | Type | Required | Description |
| -------------------------------------------------- | -------------- | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Applications** (`applicationsList`) | `list