---
sourceDocument: Australia ServiceNow AI Platform Administration
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-administration

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Review skipped records using related lists

# Review skipped records using related lists {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read

Use different related lists to resolve, track and review the skipped records in an
upgrade.

## Before you begin

Role required: admin

## Procedure

1. Navigate to AllUpgrade CenterUpgrade History.  
   A list of upgrades is displayed.
2. Select an upgrade from the list.  
   System Upgrades form is displayed.
3. Select any of the following related lists to review the skipped records.  

   Skipped Changes to Review related list
   :   Resolve the skipped update records by tracking and reviewing them in
       the Skipped Changes to Review related list. 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. See [Resolve a skipped update
       and set a resolution status](https://www.servicenow.com/docs/H11Qyibomaey52fZqDcnkg "Review the reason for each skipped record to resolve each skipped update after an upgrade.") for more information.

   Skipped Changes Reviewed related list
   :   View the list of the reviewed skipped records in the Skipped Changes
       Reviewed related list. When you select a skipped record to review
       and set a Resolution Status to a value other
       than Not Reviewed, the update record moves from Skipped Changes to
       Review related list to the Skipped Changes Reviewed related
       list.

   Copies to Review related list
   :   Copies to Review lists all the records that need to be
       reviewed.

   Copies Reviewed related list
   :   Copies Reviewed lists all the records that have been reviewed.

   Customization Unchanged related list
   :   Customizations Unchanged lists all records that were skipped (due to
       a customization), but there have been no changes from the last
       upgrade. See [Revert a
       customization](https://www.servicenow.com/docs/PVD45EvCUcBxTrchhOoE2w "To prevent customizations from being overwritten by system upgrades, the upgrade process automatically skips changes to objects that have been customized. You may want to overwrite your customizations when a software upgrade contains a feature that you would like to implement.") for more information.

   Changes Applied related list
   :   Changes Applied lists all changes that were applied in this
       upgrade.

   Claim Outcomes to Review related list
   :   During system upgrades, the Claim Status tab displays outcomes to
       review and resolve.

   Upgrade Details related list
   :   Upgrade Details lists all Upgrade Details records for this
   upgrade.  
   Note:  
   The Copies to Review and Copies Reviewed related lists are Platform specific related lists.

## Upgrade history related lists details {#ariaid-title2}

The following table gives the description of each field in all the related lists within
the upgrade history module.
{#uc-rl-details__table_b5b_p14_dlb__entry__2}

| Field | Input Value |
|-|-|
| File name | File name has different description for different related lists * Skipped Changes to Review related list: Name of skipped Upgrade Detail record * Skipped Changes Reviewed related list: Name of the reviewed Upgrade Detail record * Copies to Review related list: Name of the record that needs to be reviewed * Copies Reviewed related list: Name of the record that has been reviewed * Customization Unchanged related list: Name of unchanged sys_upgrade_history_log record. Select it if you want to access Upgrade Details and add comment text, or set a resolution status for it * Changes Applied related list: Current upgrade file name * Claim Outcomes to Review related list: Name of skipped Upgrade Detail record * Upgrade Details related list: Current upgrade file name {#uc-rl-details__ul_azl_sxk_smb} |
| Disposition | Action performed on this file during the selected upgrade: * Inserted: The system inserted a new record. * Updated: The system updated this record. * Deleted: The system deleted this record. * Skipped: The system did not change this record in order to preserve customizations. * Skipped Error: The system didn't have the upgrade on this file but skipped due to reasons like the record already exist in the system in a different scope or a system property exists. Note: This is editable only by a maint. * Reverted: This record was reverted to the base version. * Table not found: The system could not find the table that contains this record. * Unchanged: The system did not change this record because the baseline component has not changed since the last release. * Skipped Manual Merge: The system did not change this record because updating it requires manual intervention. * Skipped Apply Once: The system skipped this record because it had already applied an update from an xml file in the apply once folder. * Not Latest: The system applied a change, but this change was overwritten later during the same upgrade. {#uc-rl-details__ul_ah3_5pq_dlb} |
| Priority | Relative importance of the conflict that caused the skip. Note: ServiceNow prioritizes the skipped records based on the importance of the file types. The prioritization is done as follows: * Priority 1 (highest priority): UI pages, UI macros, and more * Priority 2: Business Rules, Security ACLs, and more * Priority 3: Reports and more * Priority 4: Form Sections, Choice Sets, and more * Priority 5 (lowest priority): other {#uc-rl-details__ul_gpz_q2j_bmb} |
| Claim Status | Outcomes: * N/A: There are no claims on the record (no need to review) * Won conflict: The loading application loaded the file but is in conflict with the previously loaded file. Recommendation: Review the two versions of the file to confirm your intended outcome. * No conflict: There may be one or more applications loading but there is no conflict. However, it is still good to review the outcome to see if it's what you intended. * Lost conflict: The file was not loaded because another application has a better claim on the file. Recommendation: Review the two versions of the file to see which should be loaded (or if they should be merged). {#uc-rl-details__ul_wwp_fyl_1fc} |
| Reason | States the reason why a particular record has been moved to the Skipped Error disposition. |
| Resolution | * Reviewed * Retained * Reverted {#uc-rl-details__ul_ycy_lqq_dlb} |
| Comment | During the process of resolving a skipped update, you have the option to add a Comment to any record. For example, the comment might explain the action that you took to future reviewers. |
| Target name | Name of the record corresponding to the current file. |
| Plugin | Plugin that contains the record. |
| Type | Current file type (such as Business Rule or UI Policy). |
| Table | Table that contains the record. |
| Changed by vendor | Indicates whether the file has been changed by the vendor since the last upgrade. |
[Table 1. Related lists details]

{#uc-rl-details__table_b5b_p14_dlb}

*[\>]: and then