On Tuesday, we implemented sprint updates in the production environment. Since that time, we have carried out several deployments on the Quality environment. Currently, the Quality environment is running nearly 7 versions ahead of what has been released in production. Today, we received a message from the product owner instructing us to roll back our changes in production, as they are causing data inconsistencies between third-party services and our applications. Please advise on the best way to proceed. We have made numerous updates across at least 10 different modules. Additionally, we continue to work on the changes that are currently in production. Please recommend the most effective strategy to roll back the changes in production without losing the new developments we have accomplished.
Hi Pradip,
Rolling back Production won't affect your Dev/Quality code, so your new work is safe. You can create a tag in LifeTime based on the previous version and deploy it to Production, steps here: https://success.outsystems.com/documentation/11/deploying_apps/rollback_to_a_previous_version/
Keep in mind that only the code is rolled back. Database changes and data stay as they are, so the inconsistencies with the third-party services will probably need a separate data fix.
Then keep working in Dev and deploy forward once it's fixed.
What Huarlem said.
The main concern is data. If you are certain it was on your side and not theirs, you have to rollback.
Some companies create a solution with the existing version in prod before doing a new deployment. It makes the rollback a simple process.
Without that, you have more manual work. Lifetime has all the deployments you did. If they went at the same time, go to the one before. If not, you need to find the applications of those 10 modules and deploy again the version from the date marked as good.
You can compare code versions in dev and move forward without the bugs created.