Skip to main content
Every config change to an install is recorded as an app config version, and any earlier version can be applied again. That is the recovery path when a rollout, or a mistyped input, turns out badly. You will need an API token (create one in the dashboard’s org settings), your org ID, and the install’s ID from nuon installs list.

​
Roll back one install

1

List the install's versions

Each entry carries the app config it pinned. The install’s Versions view in the dashboard shows the same history.
2

Confirm what changed

3

Apply the older version

Send {"plan_only": true} alongside it first if you want to see the plan without applying.

​
Roll back a deployment group

To move a whole deployment group back rather than one install, trigger a branch run against the older app config and skip the build step, since the artifacts for that config already exist:
The run still plans each group and still waits for approval, so you see the reverse diff before it is applied.
This is a pattern built from the version history and the branch run API, not a one-click button. Nothing about it is automatic: you choose the version and you approve the plan.

​
See also