Resolve skipped update records after an upgrade and transfer resolutions across instances Introduction Learn how to resolve skipped update records after an upgrade and transfer the resolutions to other instances that receive the same upgrade. After an upgrade, review skipped update records to verify that your customizations are preserved. This process can be manual and error-prone, especially when you test upgrades on non-production clones of production. You may need to process skipped records multiple times across different instances. Skipped Update Records Resolution Tracking captures your resolutions in an update set, so you can apply them to another instance and reduce the manual work after the upgrade. What is a skipped change? A skipped change occurs when your customization conflicts with an update in a new release. The upgrade doesn't overwrite your customization. If you customize a record affected by the upgrade, such as a business rule or script, the system creates a skipped log record. You then decide whether to revert to the base version, merge the changes, or keep your customization. Skipped changes can include records in the following tables: sys_ui_form_sectionsys_ui_related_listsys_choice_setTables with fields of type HTML, XML, script, or script_plain User data records, such as sys_user, don't create skipped changes. Skipped Update Records Resolution Tracking Skipped Update Records Resolution Tracking captures your customizations and skipped records dispositions, and comments in the update set. This feature is enabled by default and controlled by the glide.save.skiplist.decision system property, which is set to true by default. Details Transfer skipped record resolutions to another instance Upgrade your source instance to the target release version.Create a local update set to capture skipped record resolutions, and make it current.Process the skipped records list in the source instance.Mark the update set as complete.Upgrade your target instance to the same release version as the source instance.In the target instance, retrieve the update set from the source instancePreview and commit the update set to apply the captured resolutions. Note: The update set updates the skipped records list on the target instance, but you still need to process the skipped records list there. What the platform checks before applying resolutions Resolutions, comments, and customizations transfer only if all of the following conditions are met: The glide.save.skiplist.decision property is true.Corresponding log records exist on the target instance.The same file name exists on the target instance.The sys_upgrade_state key matches the incoming version payload hash.The Record changed field is true.The record resolution status isn't not_reviewed.The disposition is skipped, skipped error, skipped manual merge, or retrieved.The skipped record is part of the most recent upgrade. The glide.war release package (WAR) version must match the Upgrade history column in the sys_upgrade_history_log table. If any check fails, the update set reports an error. Update set warning messages If glide.save.skiplist.decision is false on the target instance, you see this message: This update will not result any action because Skipped Upgrade Records Resolution Tracking is disabled. For other issues, you see this message: This update will not result any action because it is invalid and then skip the remote update. In both cases, the only available action is to skip the remote update. To find the cause, review the conditions in the preceding section. Additional considerations If the update set contains dispositions that don't apply on the target instance, the engine reports a warning. For example, the target instance allows only Update and Delete, but the update set contains Resolve Conflicts. This means the upgrades on the source and target instances differ. To understand the differences, review the referenced upgrade history record on the target instance.Update sets work only for instance upgrades, not plugin upgrades. You can't use an update set to move or process skipped records from plugin history logs. Related Links Different number of skipped items records between instances after an upgrade Instance upgrade troubleshooting and FAQ