Why a customized instance may only show a few skipped changes during upgradesIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } If your instance is heavily customized, you may see fewer skipped changes during an upgrade than expected. This article explains likely scenarios where records in the instance will not be skipped during an upgrade and how to verify the status of your customizations. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All supported releases Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The following factors may contribute to a low number of skipped records during an upgrade, even in instances with significant customizations. Customizations outside the scope of upgrade changes Skipped records occur only when the upgrade modifies the same records that you have customized (for example, default script includes, business rules, or UI actions). If your customized components aren't part of the baseline changes in the upgrade, they remain unaffected and don't result in skips. Frequent upgrades When you regularly upgrade your instance, you reduce the number of changes between versions. This results in fewer delta conflicts during each upgrade cycle, minimizing the chances of skipped records. Customizations in Store apps or plugins If most of your customizations are in Store applications or custom plugins not affected by the core platform upgrade, these components remain untouched. Skips typically occur only in core platform tables and components affected by the upgrade. Additive changes via update sets When you implement changes using update sets without modifying default records, these changes are considered additive. Since they don't conflict with baseline elements, they don't result in skipped records during upgrade. Note: A review of the Customer Updates (sys_update_xml) table may show that many customizations were applied through update sets. Customer updates record review To verify your customizations: Randomly select several records in the Customer Updates table.Select the Compare to Current related link.If no differences appear between the selected and current versions, the customized record aligns with the current version in your instance.When there's no delta, the record isn't flagged for skipping during the upgrade. You can use this same approach to verify other records in the Customer Updates table.