Update set issue

[sonimore101]

In the Dev instance, the update set was completed, and I accidentally clicked backout. The backout process encountered a problem that was not resolved. After that, I made  update set in progress capturing some new changes. However, the original backed-out problem record is still associated with the update set. Should i moved this moved set to test instance or should i create new update to move these changes. any advice on this please? what will happen if move this update set with those problem exist in update set?

[Dr Atul G- LNG]

Hi @sonimore101 

So, you tried to back out the update and ran into issues. In that case, it would be better to create a new update, make the required changes there, and proceed with that approach. It should be good to go.

[Tanushree Maiti]

Hi @sonimore101 

To prevent configuration corruption, data inconsistencies, and missing records, do not migrate or commit this corrupted Update Set to the Test instance. It is recommended to identify and resolve the issues in the source instance first, then create and promote a clean Update Set to ensure a reliable deployment.

2-3 time I have noticed , if backout failed,  we waited for a day,  updates were properly reverted which means it worked at backend.

So I will suggest you wait for a day . check the status of updates. Create a new update set , capture the change again and move to next higher instance.