Rollbacks
Roll an app back to an earlier version on GetFlowing, by hand or automatically when a release fails its health checks.
Roll back
To go back to an earlier version, open the app's History tab and, under Releases, choose Roll back to go to the version before the one that is live, or Roll back to this on an earlier version that passed its checks. The version running now is marked Live now.
A rollback deploys the earlier commit again, with the same build and health checks as any deploy. Your newer code stays in your repository, and you can deploy it again later. A rollback does not undo changes to your database.
A rollback always needs approval. If you are an owner or admin, confirming the rollback approves it. A rollback counts as a deployment: it still works when your workspace is over its plan's limits, but not once the month's deployments are used up. See A plan limit was reached.
Automatic rollback
GetFlowing also rolls back by itself. With Auto-rollback on failed health checks on, which it is by default, a release that goes live and then fails its health checks is replaced by the last working version. On plans with the agent, this happens once the agent has tried to fix it. A release that never came up is also cleaned up, instead of being kept for you to look into.
The setting is in Settings, under Workspace, on the Deploys tab (called Agent and deploys on plans with the agent), under Approval policy.