Washington DC upgrade query

[JohnnySnow]

Hi Team,

We have recently upgraded our dev instance from Vancouver to W-DC, and there are few skipped logs with the disposition of Skipped Error. I have reviewed this article(KB0786212) and I'm setting the logs to Reviewed. However, I observed that few of the logs are not getting captured in the update set (neither in my custom update set nor in the default update set) but the details are saved properly.

Does any one know what the reason is? has some one faced similar issues?

[Mark Roethof]

Hi there,

Actions taken on Skipped Records are captured in Update Sets as "Upgrade Details". This is since a few releases like this and makes handling Skipped Records over multiple instances easier, since now also the "administration" of the Skipped Records is captured and you don't have to do this over and over on every instance (unless there is a difference in number of Skipped records ofcourse, which in most cases is caused by out of sync instances / instances still being developed on while upgrading / upgrading to different patch/hot fix levels).

For the Skipped records with Disposition "Skipped Error" I would advice you to create a Skipped Record Rule (introduced with Vancouver). This way these Skipped records will automatically be handled for you and saves you again time and effort. Skipped Error should be handled with "Reviewed" according to ServiceNow Support.

Read about Skipped Record Rules in one my articles:
- 2024-03-15 - Article - Exploring Upgrade Center Skipped Record Rules

Or see this example from a customer:

[JohnnySnow · Accepted solution]

Hi Team,

This is what I observed after researching on the issue, any skipped logs which are generated for private application wont get captured in any update set. So any such records need to be processed manually in each instance.