Instant Rollback
Last updated on June 26, 2026
Instant rollback re-pins every production Station to a previously built Deployment. There is no rebuild: the active pointer flips, and stations pick up the change between Runs.
What changes
The table below shows exactly what rollback touches and what it leaves alone.
| Rolls back | Does not |
|---|---|
| Active deployment on every station linked to this procedure. | Runs already uploaded. They keep their original deployment ID. |
| The procedure version operators see. | Git history. |
| Auto-push. It pauses until you push another deployment to all stations or resume it from the banner. | Other procedures on the same stations. Rollback is per-procedure. |
Rollback does not delete the bad deployment. It stays in the registry and can be re-pinned.
Roll back
Follow these steps to roll back from the dashboard.
Open the procedure and go to Deployments.
Open the ⋯ menu on the deployment to return to and select Instant Rollback. Eligible targets are production deployments with a ready build. Preview deployments and failed builds are not eligible.
Review the confirmation dialog. It shows the current production deployment and the rollback target side by side.
Confirm. Every linked station is re-pinned and picks up the change between runs.
While rolled back, the deployments page shows a banner. Auto-push stays paused until you push another deployment to all stations or click Resume auto-push in the banner. Resuming does not repoint stations — they keep the pinned deployment until the next push replaces it.
API and SDK support for rollback is planned but not available yet. Rollback is dashboard-only for now.
How is this guide?
Rolling RolloutPreview
Learn how to promote a new TofuPilot deployment one station at a time so you can validate the build on a canary before going wide.
Import
Learn how to import existing test results into TofuPilot from OpenHTF, WATS, STDF, ATML, CSV, and Excel files without changing your test code.