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. On the install, Configuration → App branch → Applied config history shows the same list.
2

Confirm what changed

The diff for a VERSION_ID is the component change recorded for that version:
3

Apply the older version

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

Roll back an install group

To move a whole install 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.
Rollback re-uses the version history and the branch run API: you choose the version, and you approve the plan before anything is applied.

See also