skipped upgrade items show no difference when attempting to resolve

[TT21]

Have just completed the upgrade of non prod instance from Rome Patch 9b to Tokyo.
Running the Upgrade Preview showed 59 records predicted to be skipped and reviewing these they contained customisations. After running the upgrade there were 411 skipped records to review. 380 of these are sys_security_acl settings and when attempting to resolve conflicts the screen show message "There are no differences found". A check of the upgrade log shows an entry like "Skipping because of database override: update/sys_security_acl_ffed35d2c72010100a9b5d83c7c26046.xml" for each one. Reviewing the differences shows the base has the sys_id for the Operation and the Customized has the friendly name - no other differences could be seen.
Is their anything I can do to stop it generating these skipped records and\or avoiding having to address each one ?

[Zach Koch]

Unfortunately, whenever you make a change to something baseline, it will be marked as a customization.  After changing something, even if you change it back to the same values, it will still be marked as a customization by the system, and in those cases best practices is to revert the version to revert the change making it baseline again and it won't be a skipped record.  I included some links to potentially help you.

Support article on customizations

Customization best practices

If this helped resolve your issue, please mark this correct and helpful, thank you!

[TT21]

Thanks for your reply - These 300 odd items we have not changed, they are as they came its the upgrade has either not recognised this or what ever the process that is generating the  "Skipping because of database override..."

[FYL]

Same here.

I am upgrading a new instance from San Diego Patch 7 to Tokyo Patch 2 and over 400 skipped changes that had no changes nor authorized to be updated. 
Any has an explaination to this or I assume we are just going to have mark them as Reviewed and leave them as is. 

[Annmol Perayil]

Hi Kilo, I am experiencing the same issue. 609 P2 skipped records, with Change type  as 'No code change'. Please let me know as well if you get any response from anywhere. I have logged a case with ServiceNow and also, asked our Solution consultant. I will let you know as well, if I hear back.