What does skipped error mean in Upgrade history and how to resolve it?

[szollo]

Hello,

This is the first time I'm carrying out an upgrade(I'm new to ServiceNow) and reviewing the Upgrade History I have found that there are ~70 Skipped Error. We have upgraded from Fuji to Geneva.

I can see that I can resolve Skipped conflicts, but it seems there is nothing I can do with Skipped Errors(like resolving those or unsure how to execute it again/seeing errors etc). The only thing I can see is this:

I tried to customise the layout and it seems the only valuable thing I can see is the "Payload", but as I mentioned I don't have too much knowledge in this.

What shall I do with the Skipped Errors?

Unfortunately the documentation I saw is not really helpful, basically saying that "Count of upgrade records skipped because an error occurred."

Any help/guidance would be appreciated.

[sergiu_panaite · Accepted solution]

Hello Gergely,

There can be several reasons for why you get records marked with 'Skipped Error', like for example a system property exists and is only editable by maint or uneditable. Unfortunately the name is a bit confusing as usually 'Skipped' records in upgrade are the ones that have been customized by customers.

Regards,

[peterraeves]

With our upgrade (from GP6 to GP6HF2), out of 44 Skipped Errors, 36 are System Properties. So pretty basic issue, but how do we resolve this issue? What should we do to these System Properties to prevent them from erroring during production upgrade?

[richfred]

These "skipped error" records in the upgrade history usually contains sys_properties data, that may already have been set in your instance. You can review the conflicting data to confirm the values and if the values are the same, you can leave the record as skipped. Most of these skipped error records also has a Priority of 5(low).

when you do a check on the skipped error records your will see that mostly the reason why this was the disposition of these updates is that it belong to a Scoped App Author or the Scoped App Client applications. Take note that these sys_properties are existing in your instance already.

Opening the Show Related Record link for these records results to the message below and no option to edit the record at all:

"This record is in the Scoped App Author application, but Global is the current application. To edit this record click here."

In comparison, open a record with Disposition "skipped" and you will have the options to Resolve Conflicts(comparison of Base system vs. Custom)or Revert to Base System.

Lastly, based on the Priority grade of these skipped error records should not have any effects on the behavior and functionality of your instance.

[Tarun9]

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0786212

There's no need for anything to be done on these records. You can safely ignore these records and set the status on these records as Reviewed.