Actions on skipped records post Vancouver upgrade

[Swetham]

Hi all,

We had our instance upgraded to Vancouver Patch5 and we have list of skipped records.

When we deployed the update sets related to actions taken from lower instances, many records still stay skipped in PROD. 

Since it's prod, we cannot manually take action on these. 

How to approach this.. any inputs would be greatly appreciated.

Kind Regards!

[Mark Roethof]

Hi there,

Did you also include the Upgrade Details records in your update set, which get created when handling the individual Skipped Updates?

[Swetham]

Yes, Mark.. The only thing is, my prod was upgraded to patch4 hotfix1 and then patch5... so when we saw the upgrade history, patch5 had 6 records to review and patch4hotfix1 had 65.. after deploying the update sets, patch5 now has only 2 records to be reviewd but in upgrade history, patch4 htfix1 has 63 records... so the update set custom updates were skipped

[Mark Roethof]

Ahhh yes, unfortunately that is a known thing when performing upgrades, best practice is to upgrade on to exactly the same release / patch / hotfix.

So your lower environments are now also on the same version I guess? Could you redo the Skipped Updates there and fetch them in an Update Set to process this again.