Environments and releases
Roll back a release
Put Staging or Production back on a release it ran before, straight away. Only releases the environment ran before, admins only for protected environments, and the current release stays in the list.
Guide2 min readUpdated 1 November 2026
Rolling back puts an environment back on a release it ran before, straight away. The release it runs now stays in the list, so you can promote it again once it's fixed.
Before you start
- You're a workspace admin, for a protected environment (Production by default); an editor can roll back environments that aren't protected.
- The environment has run another release before. A new environment, or one that has only ever run v1, has nothing to go back to.
Steps
- 1
Open the environment
On the agent's page, click the Production (or other) pill in the environment bar.
- 2
Choose Roll back
In the banner. The dialog, Roll back Production, lists the releases this environment ran before, newest first, with their notes and who made them.
- 3
Pick the release and confirm
Select one and choose Roll back to v2. The toast reads "Production runs v2 again".
You're done when
The bar reads Production · v2 · just now, the Deployment history has "Rolled back to v2 from v3", and the next message in Production is answered by v2.
After a rollback
- Only that environment changes. Staging keeps running v3 and Development keeps its draft. To put v2 in Staging too, roll Staging back as well.
- v3 stays in Releases. Promote it again when it's fixed: a release running in an environment can be promoted on from there; one running nowhere needs an environment rolled back to it first.
- Rolling back doesn't change the draft. If v3 was wrong, fix Development and promote a new release, v4, rather than staying on v2.
- Every rollback is in the audit log: "Rolled <agent> in Production back to v2".
If something goes wrong
Roll back is greyed out
The reason is on hover: the environment hasn't run another release yet, only workspace admins can roll back a protected environment, or viewers can't roll back.
"Production never ran v1, so it can't go back to it."
An environment only rolls back to releases it ran before. To run v1 there, promote it along the path: roll Staging back to v1 first, then promote.
Does a rollback cost anything or lose conversations?
No. It changes which release answers from the next message; conversations and traces stay.
Related
Still stuck?
Email us with what you tried and any request id. A person replies.