Backing out a catalog item from production that has multiple update sets

[Mike LHCG1]

When requesting to move a catalog item to production, we need to provide a detailed backout plan in our change requests. I have a catalog item that has 5 different update sets that need to be imported, previewed and committed. I believe only the last update set can be backed out, so if something goes wrong, how can that catalog item be backed out and reverted back to the exact working state before the change started? Thank you!

[ThomasAnnan · Accepted solution]

Have you considered merging the update sets so that you only have to commit 1?