Rollbacks

A rollback returns a service to a previous successful build. When a new release misbehaves, you don't have to debug under pressure — restore the last working version in minutes.

How it works#

Every successful build is stored as a rollback point.
Those builds are marked with a Roll back button in the deploy history.
A rollback restarts the service on the stored version — no rebuild runs, so the return is fast.
The number of stored rollback points is limited: old ones are evicted by new builds.

What a rollback changes — and what it doesn't#

Reverts to the previous version	Stays current
Application code and the built image	Environment variables
Start commands from that build	Data in volumes
Dependencies pinned in the build	Database contents
	Domains and ports

Schema changes need data recovery too

If the new version already altered the database schema, rolling back code is not enough — you also need to restore data from a backup.

Rolling back a service#

1
Open the Deployments tab
Open the service → Deployments.
2
Find the deploy to return to
Use the timestamp and status as a guide — only successfully finished builds are available.
3
Press Roll back and confirm
Confirm the action in the dialog that appears.
4
Wait for Running
A "rollback started" notification appears. Wait until the service status becomes Running, then check the application.

To see what exactly changed, expand the deploy: the full build log and a Copy button are inside.

Rollback points are stored automatically on deploy, so there is nothing to set up. The behaviour can be managed on the service Settings tab. If the feature was ever disabled, no rollback points exist for that period — only builds made after it was re-enabled.

Recommendations#

Roll back first, investigate later

Restore a working version, then read the failed deploy's logs without rushing.

Keep migrations reversible

Design schema changes so the previous code version keeps working.

Back up before a big release

Then you can roll back both code and data.

Verify after rollback

Check the key flows: sign-in, payments, form submissions.

Rollbacks

How it works#

What a rollback changes — and what it doesn't#

Rolling back a service#

Storing rollback points#

Recommendations#

FAQ#

Can I roll back several versions?

How long does a rollback take?

There is no "Roll back" button — why?

Does a rollback affect domains?