Add to Update Set Utility version still not updated after committed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2024 01:30 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2024 06:43 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2024 09:32 AM - edited 05-20-2024 10:53 AM
Seems some semaphore or mutex didn't get released, you can create a Support Case for hosted (not PDI) instances to get that reviewed. However, what you show is a typical commit log, and that doesn't indicate anything is stuck, just a poor choice of words.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2024 11:05 AM
Thank you for your reply. No issue has been found when I was doing this in PDI. I will go ahead and create HI case with ServiceNow.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2024 11:10 AM
I see that the following on sys_update_xml.list for: sys_ui_action_131e99ed49e8950002ad45cc9609026f
<replace_on_upgrade>false</replace_on_upgrade>
so that would explain the new version not being present. However, I see that ui action record doesn't differ from the version added back in November in my PDI.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2024 11:13 AM
PDIs are not supported, no need to create a Support Case for that.