Roll back a release

Rollback is never an untracked reversal. It is a new plan that references a previously successful release in the same environment and goes through its own approval and run.

Who can do this

Workspace Owners and Administrators with the rollback approval capability, which is evaluated separately from deployment approval.

Create the rollback plan

1. On Deployments → Overview, find the succeeded plan you want to return to and choose Plan rollback here.
2. The confirmation shows the environment, the rollback target release, its plan hash, and its source commit. Choose Create rollback plan.

The new plan copies the target’s release (version, commit, artifacts) verbatim and uses the environment’s current workflow and connection revisions. Nothing executes until it is separately approved and started.

Approve and run

Follow Approve and run a deployment. Before execution the target is re-checked: it must still be a succeeded plan in the same environment and service with the same release and artifacts, or the run fails with The rollback target is no longer valid.

When rollback is unavailable

A workflow supports rollback only when every promotion, execute, and test step in it does. The Terraform and OpenTofu saved-plan adapters do not, so an environment using them cannot produce a rollback plan. See the adapter catalogue.