--- sourceDocument: Xanadu ServiceNow AI Platform Administration sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/platform-administration Release : - xanadu ft:locale : - en-US ft:publication_title : - Xanadu ServiceNow AI Platform Administration ft:clusterId : - platadm bundleId : - platadm workflow : - Platform --- # Process the skipped records list # Process the skipped records list {#ariaid-title1} * Release version: Xanadu * * Updated August 1, 2024 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read If you customized or altered a record affected by this upgrade, such as a business rule or script, the upgrade generates a skip log record. You must resolve the differences between the upgraded and customized versions of the record by processing the skipped record list, or, in other terms, just processing the skipped list. ## Before you begin Role required: admin ## About this task Review the changes you made to baseline records, such as business rules and scripts, that appear on the skipped records list and revert to the baseline version if appropriate. Post-upgrade, thoroughly test all changes you made to these records. ## Procedure 1. If necessary, navigate to System DiagnosticsUpgrade Monitor. If the upgrade is still in progress, the system displays the [Upgrade Progress](https://servicenow-prod.fluidtopics.net/KVf4hpjOHrbJbJOMq1yweA "When an upgrade is underway, Upgrade Progress displays progress bars and other information to help monitor the process.") screen. When the upgrade finishes, the system displays the [Upgrade Summary Report](https://servicenow-prod.fluidtopics.net/FYZOLycuN9dzcr607VMNdw "This report summarizes the actions taken, provides tools to resolve conflicts between customizations and the upgrade, and provides information to help estimate time for upgrades to other instances."). 2. After the system displays the Upgrade Summary Report, click the Click here link in the Skipped box. The system displays the [System Upgrades form](https://servicenow-prod.fluidtopics.net/459KLF2dl1FtIqiT1FFS0g "When an upgrade is complete, the System Upgrades form displays key statistics about the upgrade and a related list of skipped records (the skipped list)."). 3. Navigate to Review Skipped Records section and -- if necessary -- scroll to the [Skipped Changes to Review related list](https://servicenow-prod.fluidtopics.net/bDXSMEIzh5ke1wvTsSDMyg "To prevent your customizations from being overwritten during system upgrades, the upgrade process skips (does not apply the update to) objects that have been customized. To assist you in tracking and resolving skipped update records that need review, Skipped Changes to Review lists all updates skipped during the upgrade process."). 4. Click the row for the first record you want to reconcile. The system displays the [Upgrade Details form](https://servicenow-prod.fluidtopics.net/d_GOOUNjb9b~vUH38nlEMg "From the Upgrade Details form, you can review an individual record affected by the upgrade and reconcile conflicts between the upgrade and customizations.") for that record. 5. Evaluate how you want to resolve the conflict for this record and take the appropriate action. {#upgrademon-process-skip-list__cho_OverwriteCustomization}{#upgrademon-process-skip-list__jcj_yjc_fx} | Action | Description | | Retain the customized record as is and do not update it. | After reviewing the changes, set Resolution Status to Reviewed and Retained.{#upgrademon-process-skip-list__zxx_5lc_fx} The record moves from the Skipped Changes to Review to [Skipped Changes Reviewed related list](https://servicenow-prod.fluidtopics.net/pGDp3arviXvu1KIRBqoXyA "Skipped Changes Reviewed lists update records that previously appeared on the Skipped Changes to Review related list and have been reviewed. When you select a skipped record to review and set a Resolution Status to a value other than Not Reviewed, the update record moves to the Skipped Changes Reviewed related list."). | | Retain the customization by merging changes from the updated object. | 1. Click Resolve Conflicts to navigate to the [Resolve Conflicts form](https://servicenow-prod.fluidtopics.net/pyY4emWqr_NGvHEorLdFnw "The Resolve Conflicts form you compare to the base system version with the customized version of a record and reconcile the differences."). 2. Review the differences. 3. To merge a field: * Click the right-arrow button for the field. * Click a text box to view and edit the detailed differences. * When you have merged all appropriate fields, click Merge. {#upgrademon-process-skip-list__ul_gnl_sh1_xbb} {#upgrademon-process-skip-list__ol_amy_mbt_wbb} After merging the customization changes: * The Disposition changes from Skipped to Merged. * The Resolution Status changes to Reviewed and Merged. * The record moves from the Skipped Changes to Review to the Skipped Changes Reviewed related list. {#upgrademon-process-skip-list__ul_mgl_nrp_ps} | | Discard the customization and update the record to match the base system for this upgrade. | After reviewing the changes, click Revert to Base System. * The Disposition changes from Skipped to Reverted. * The Resolution Status changes to Reviewed and Reverted. * The system creates a Customer Update record. * The record moves from the Skipped Changes to Review to the Skipped Changes Reviewed related list. {#upgrademon-process-skip-list__ul_qzm_lrp_ps} Note: At any time after you revert a customization, you can click Reapply Changes to reapply the customization (undo the revert). | | Review the skip and perform no action on the object. | After reviewing the changes, set Resolution Status to Reviewed. The record moves from the Skipped Changes to Review to the Skipped Changes Reviewed related list. | | Leave on the skipped list for a later decision, and note that you have not reviewed the record. | From the Resolution list, choose Not Reviewed to defer the decision on how to handle this conflict. The record stays on the Skipped Changes to Review related list. | |-|-| {#upgrademon-process-skip-list__choicetable_fg3_mmp_ps} Note: The system tracks changes to records in an update set so you can apply these changes to another instance later. However, the system does not migrate the upgrade details records from one instance to the next. These records apply to a specific upgrade of a specific instance. If you want to preserve the Comments, Resolutions, or other information from the skipped list, export it from this instance. 6. In the Comment field, write the reasons for making your decision and other information you want to document. {#upgrademon-process-skip-list__y4s_mmc_fx} 7. Click Update. Post-upgrade, thoroughly test all changes you made to the records on the skipped record list. {#upgrademon-process-skip-list__yb2_qmc_fx} * **[System Upgrades form](https://servicenow-prod.fluidtopics.net/459KLF2dl1FtIqiT1FFS0g)** When an upgrade is complete, the System Upgrades form displays key statistics about the upgrade and a related list of skipped records (the skipped list). **Related reference** * [Debug upgrade](https://servicenow-prod.fluidtopics.net/NsVtOCn9VdyvQLYqN17NiQ "Diagnose and resolve issues you suspect may have resulted from the most recent upgrade by enabling upgrade debugging during a user session. Each transaction lists whether an artifact was skipped, customized by the customer, or modified by ServiceNow during the last family-to-family or patch version upgrade.") *[\>]: and then