Rollback
Switching the live app back to an earlier version when a new release breaks something.
What it is
A rollback puts the previous working version back live, fast, while the problem gets fixed properly. It's the emergency brake for deploys.
Rolling back the code is usually easy. Rolling back data is harder: if the broken version already changed or deleted records, those changes don't automatically reverse.
A good habit after a risky deploy: know which version you'd roll back to, and check the main flows right away.
How to ask for it
“The new version broke everything, put the old one back.”
“Roll back production to the release from yesterday afternoon, before the checkout change. Then check whether any orders placed since the deploy were saved incorrectly, and list them.”
"Put the old one back" doesn't name a version or address data; the prompt specifies the target and checks for damage.
You've seen this in
- AA site quietly returning to its old design after a bad launch
- SStatus pages saying "we've reverted the change"
- SApp updates pulled from stores