Unable to back out Update Set and receiving an error : One more more versions were not able to be backed out. Details can be found in the system log.

[Navneet Arora]

I am facing a strange issue while backing out an update set as shown in image

Initially we had 20 update sets which have child-parent hierarchy defined in a batch base. So i did try to back out batch base directly which caused some errors. Then i opened all 18 update sets and tried to back out individually , and i was able to back out many . But 2 update sets are showing this error continuously and are not getting backed out.

Also, the update sets include portal related changes (widgets , images etc. ). I checked in system logs as well but didn't help much .Please suggest how to back out so that I can re-migrate new update set with correct changes.

[Sajilal]

Since you have tried both now backing out parent batch as well as individuals, something might have gone wrong in terms of sequence etc. For now you can just recapture the parent batch again and move it to the same instance, then check if there anything missing so that you can capture it for your higher instance move.

Hope this helps!

Please Mark as ✅ Correct if this solves your issue and also mark ???? Helpful if it helps resolve your problem.

Thanks,
Saji

[congrh]

When I create a new table and then back out of this update set, this issue occurs. Have you resolved it?