A rollback is useful only when the previous application version can still run against the current data and services. Plan that compatibility before an incident rather than while users are waiting.
Keep the recovery inputs ready
- Retain the exact previous build artifact and its configuration reference.
- Separate database migrations from code release and make schema changes compatible with both versions where possible.
- Document who can initiate a rollback and how the change is recorded.
Verify behavior after restoring
Check the affected route, error rate, and key user task after rollback. Watch for background jobs or cached assets that may still use the new behavior.
A rollback restores code, not necessarily data that has already changed. Include a recovery or forward-fix plan for irreversible operations and test it in a safe environment.