Add a runbook for rolling back post-deployment migrations
In this incident, (production#2731 (closed)), The Database team was involved early in the process. The problem was diagnosed, a solution was found and a fix was ready at the quickest possible timeframe. We could have fully reverted the migration and reduce the time to mitigate the issue by 30-60 minutes, but as a stable solution was found, we decided to fix the problem even with an additional introduced delay. Given that, the only part of the mitigation plan that could be improved in similar cases is rolling back a migration in staging or production.
The purpose of this issue is creating a generic Runbook for rolling back post-deployment migrations, taking into account the experience of the successful rollback in this incident.
Edited by Alberto Ramos