Glossary · RollbackAlso called revert, staged rolloutChecked 27 September 2026
What is a rollback, and why ask whether it has been tested?
A rollback is putting the previous working version back. It only counts if somebody has done it, because the first attempt always uncovers something: a migration that does not reverse, a cache holding the old shape, credentials nobody has. A rollback plan written down and never run is a hope with a procedure attached.
In one linePutting the last working version back, on a path somebody has walked.
Why it matters to you
The cheapest version is the one that shares a path with ordinary work. On octyn.co, rollback is a revert and a push, which is the same path as any deploy, so there is no separate emergency procedure to get wrong under pressure. A build that does not compile never replaces the running container, so a broken commit leaves the live site untouched.
Mobile is different because the store is in the way, so Mooney rolls back through the Play staged rollout: a bad build halts at a percentage instead of being recalled.
The harder case is the data, which a code rollback cannot undo. If the system wrote something wrong to a database, going back to the old version does not unwrite it. That is why rollback questions should always be asked twice, once about the code and once about the rows.
If a proposal used this word and did not explain it, ask us.
The first conversation is with the people who would build it. If there is a fit, the Consult comes next.