Hundreds of skipped changes - upgraded from San Diego to Tokyo

[Chris Dea1]

Hi all,

We are upgrading our instances from San Diego to Tokyo within the next week.  To get a general/ballpark idea of the number of skipped changes I upgraded my PDI from San Diego to Tokyo...  I was alarmed to see 382 P2 skipped changes and 52 P5 skipped changed.  I noticed the P2 skipped changes have "Change type" of "Code unchanged" and the P5 skipped changes say "Unable to determine" or "Code unchanged".  I found this post here.  The person in that post basically experienced what I am seeing and the resolution seems to be to mark them all as "reviewed"....

Have anyone else experienced this same thing when upgrading from San Diego to Tokyo?  Can you confirm how you handled the P2 and P5 skipped changes? (mark as "reviewed"?).  Is there a way to change the skipped changes in mass so I don't have to change each one manually? 

Thanks for any advice!  I am hoping to get more info about handling this so that I can keep my sanity after the Tokyo upgrade.  I submitted a ticket to support to ask them as well but I am very interested to see what steps others have done to handle this situation.

Screenshots attached showing the P2 and P5 incidents after Tokyo upgrade.

  

Best,

Chris

[Bert_c1]

Hi,

You can start here:

https://docs.servicenow.com/bundle/tokyo-platform-administration/page/customer-support/concept/skipp...

Good luck, you have some review work ahead of you.

[Chris Dea1]

Thanks for the reply.  Since our instance is very close to OOB this not not seem normal based on post,  see link referenced.  Anyone else have similar experience with upgrade going from San Diego to Tokyo?

[Bert_c1]

I see in a demo instance, upgrade from Rome to Utah resulted in 77 Skipped updates. I saw your screenshots. Use the "Upgrade Monitor" to manage those. I have no other thoughts on this, but if you think any are wrong then create a Support Case and have the upgrade logs reviewed.