How to find backout update sets

[attanhes]

Hi

We have created update set in DEV instance and captured some changes and was in 'completed" state to ready to move to PROD, unfortunately some other developer clicked on "BACK OUT" this update set by accident.

Where I can see this update set? I can not find this update set in anywhere within the instance under "Retrieved update sets" or "Local update set".

Also I followed below but still no luck. 

https://docs.servicenow.com/bundle/orlando-application-development/page/build/system-update-sets/task/t_BackOutUpdateSet.html

Also checked that on audit deleted records logs but still no luck...

Looks like this update set completely wiped off leaving without any clue. However i can in the logs under sys_progress_worker.list this update set has been "backed out"

https://instance.service-now.com/nav_to.do?uri=%2Fsys_progress_worker_list.do

Also this update set can not find under sys_update_xml.list as well..

I really appreciate if anyone can provide some infor to find this update set

[MrMuhammad]

Can you go to any of the record (e.g. UI policy, business rule etc) that was captured in the Update set and bring in Versions related list on the record form. In the Version related list you will find out the captured updates with Update set name under Source column. From there you can find out, if by chance that update set is not completely wiped off. 

Btw, backout updates sets still remain in retrieved update sets and do not delete from the instance.

Please mark this accepted & helpful if it answered your question.

Thanks & Regards,
Sharjeel

[attanhes]

Unfortunately that was not the case. I already went into updated script and version controlled and tried to find this update set but it was decoupled during the backed out process.

Also I have tested this in my personal development instance but I could not find when update sets backed out where it goes. I am missing something here...

[Gaurav Shirsat]

Hi Attanhes

Backing out an update set creates delete updates in the current update set. If you commit, back out, and then reapply a remote update set, errors appear in the previewer because the deleted updates are considered more recent changes and cause collisions.

Do not back out the Default update set. This action can damage the configuration of the instance.

The back out process reverses both record-level updates and changes to the dictionary. Some changes caused by a back-out can result in data loss. These are the expected results of the back-out process:-

Note: If you commit, back out, and then reapply a remote update set, errors appear in the previewer because backing out an update set creates delete updates in the current update set. The deletes are considered more recent changes and cause collisions.

Batch update sets enable you to group update sets together so you can preview and commit them in bulk.

Dealing with multiple update sets can lead to problems, including committing update sets in the wrong order or inadvertently leaving out one or more sets. You can avoid these problems by grouping completed update sets into a batch.

The system organizes update set batches into a hierarchy. One update set can act as the parent for multiple child update sets. A given set can be both a child and parent, enabling multiple-level hierarchies. One update set at the top level of the hierarchy acts as the base update set.

When you preview or commit the base update set, you preview or commit the entire batch. The system determines the processing order, and checks for collisions, based on the dates the changes were recorded, and on their sequential ancestry. Their ancestries are the specific instances in which the changes in the update sets took place.

Please Go Through the Docs:-

https://docs.servicenow.com/bundle/orlando-application-development/page/build/system-update-sets/tas...

https://docs.servicenow.com/bundle/orlando-application-development/page/build/system-update-sets/hie...

 Please Mark Correct and Helpful

Thanks and Regards

Gaurav Shirsat

[pbusch]

Very infromative, thank you Gaurav.