argocd app rollback: Revert to a Prior Sync
argocd app rollback redeploys a previous revision of an Application using an entry from its deployment history.
When a deploy goes bad, rollback re-syncs the Application to a known-good history ID without needing to revert Git first.
What it does
argocd app rollback re-applies a Application to a previous revision identified by a history ID from argocd app history. It performs a sync to that stored revision. Rollback is blocked while auto-sync is enabled, since auto-sync would immediately re-apply Git.
Common usage
argocd app history guestbook
# roll back to history ID 3
argocd app rollback guestbook 3
argocd app wait guestbook --health --timeout 300Options
| Flag | What it does |
|---|---|
| <APPNAME> <ID> | Application name and history ID to roll back to |
| --prune | Prune resources during the rollback sync |
| --timeout <sec> | Fail if the rollback sync does not finish in time |
In CI
List IDs with argocd app history first; the ID is the deployment number, not a Git SHA. If the app uses automated sync you must disable it (argocd app set --sync-policy none) before rollback, then re-enable it once the Git fix lands.
Common errors in CI
"FATA[0000] rpc error: code = FailedPrecondition desc = Rollback is disabled for the app with automated sync enabled" means you must turn off auto-sync first. "application ... has no history" appears on an app that never synced. An out-of-range ID gives "history not found".