Roll back a deploy

Restore the previous build when a release fails.

When a deploy breaks production, you need to recover fast. Rolling back restores the previous build in seconds — no rebuild, no redeployment, just instant recovery.

Your team stays informed: the rollback reason is recorded on the deploy timeline so everyone knows what happened and why.

1

In Deploys, open the release to roll back.

In Deploys, open the release you need to back out of.

 

2

Set Roll back to; rollbacks reuse the existing artifact and complete in seconds.

Choose the build to restore — rollbacks reuse the already-built artifact, so they complete in seconds.

Rollbacks reuse the already-built artifact, which is why they complete in seconds instead of minutes.

3

Click Roll back now; the reason is recorded on the deploy timeline.

Click Roll back now. The reason is recorded on the deploy timeline for your team.

 

The reason you provide is recorded on the deploy timeline for your team to reference later.

 

4

Production serves #4820 again; the rolled-back deploy stays in history for diffing.

Production now serves #4820 again. The bad deploy stays in history so you can diff what changed.

 

What's next

Once production is stable again, review the deploy timeline to understand what changed and why the release failed.

Then investigate the root cause and prepare a fix for your next deploy.