Update set Back out - Points to considerDescriptionPoints to consider before Backing out an updateset The Impact of backing out an updateset is a bit tricky one as ServiceNow cannot benchmark as this is of a broader nature. We are not sure what are the customisations involved like ( did the update-set created/removed/modified fields and length and the additional configurations) and how this works with the existing configurations ( customised and OOB). So, backing out the whole update-set for a small subset of issue is NOT something which I personally recommend even though there is an option. For one feature which is not working, you are backing out all the customisations went with that update-set and quite a few schema level configs cannot be backed out and it will stay there ( as it can create data loss). So a Backout will not bring the instance to a clean slate as in before the update set commit. Why Backout doesn't work for some scenarios is more from an operational point of view than from a functionality point of view. Few example scenarios are like:- A field/Table got added and by the time the backout happen, there are records created on that field. If we undo the field creation; it is Data loss.A field was modified for Length where now it starts accepting more data and if we undo the field schema modification; all the data created from the length alert to update set backout is lost. This doco says what cannot be backed out and what are the expected behaviour of the commits. Back out an update set So, to cover these anomalies; some configurations are never backed out to keep the instance in a steady state Recommendation if there is a backout Scenario is as follows:- Clone PROD to DEV and TESTFix the issue on DEV and create a new update-set for the FIX.Commit FIX on TEST and see how it goes.Commit the FIX on PROD. You can also clone PROD to SUBPROD and then back-out the update-set and test if you are getting the intended result set and then do the same on PROD after weighing in the impact. It will be an organisational decision to decide how to move forward based on the gravity of the situation and how fast you need the resolution. Update set Backout will not bring the instance to a clean slate as in before the update set commit. There will be residue of the update-set on the instance even after a backout.