Skip to main content
Use a release when you want to label and promote the current live state. Use a rollback when you want to move traffic back to an earlier deploy.

​
Start with deploy history

Deploy history tells you what is live now and which deploy IDs are valid rollback targets.

​
Promote a release

Promote takes the latest live dev deploy and deploys it to production. Optionally tag it:
You do not specify a deploy ID, promote always acts on the current live dev deploy. Choose this flow when dev is healthy and you want a stable production release.

​
Roll back to a previous deploy

Use rollback when the live deploy needs to be replaced immediately:
The rollback target must come from floo deploys list --app my-app. A rollback re-points traffic at the earlier image and does not run migrate_command; it is not a schema downgrade.

​
Which one should you use?

If production is unhealthy:

​
Dashboard surface

The shipped app detail view has a Releases tab for promoted releases. The CLI remains the primary surface for choosing rollback targets and executing the rollback itself.

Logs and debugging

Read build and runtime logs before deciding whether to roll back.

Environments

Dev vs prod, promotion, and per-environment overrides.