- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2023 11:10 AM
When I'm applying an update set that is batched, sometimes I get an error saying Update set commit Failed at 100%.
But if I check the individual update sets, they are all committed. The commit log shows only entries of info type and no errors.
Is it ok to ignore this error message? Is there a way of knowing what exactly triggered the commit error message?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2023 11:53 AM
Hi,
In the commit log, there should be a bit more information as far as what happened.
I've seen this before and the scenario was that there were images included in the update set (that were uploaded to the image library -- i.e., in knowledge) and when the commit went to take place, it wasn't an actual issue with the update set, but the images already existed in that environment (don't ask me how) and so the "duplication" was rejected...thus it shows that the update set failed even though it got to 100%.
So, basically, in your log, there may be messages that like that that can explain what took place.
Overall, it should be fine.
Please mark reply as Helpful/Accept Solution, if applicable. Thanks!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2023 11:38 AM
Test what you updated and maybe check system logs?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2023 11:53 AM
Hi,
In the commit log, there should be a bit more information as far as what happened.
I've seen this before and the scenario was that there were images included in the update set (that were uploaded to the image library -- i.e., in knowledge) and when the commit went to take place, it wasn't an actual issue with the update set, but the images already existed in that environment (don't ask me how) and so the "duplication" was rejected...thus it shows that the update set failed even though it got to 100%.
So, basically, in your log, there may be messages that like that that can explain what took place.
Overall, it should be fine.
Please mark reply as Helpful/Accept Solution, if applicable. Thanks!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2023 02:01 PM
Thank you. That was helpful. This normally happens to me when I'm applying a batched update set. Commit log is long for these cases and next time I'll evaluate them closely.