--- 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 --- # Upgrade History module: Track every upgrade # Upgrade History module: Track every upgrade {#ariaid-title1} * Release version: Xanadu * * Updated August 1, 2024 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read The Upgrade History module tracks every upgrade made to an instance. Administrators can use the module to resolve upgrade conflicts and optionally to revert customizations to base system versions to take advantage of new features. An upgrade history record is created for each upgrade that is run. To view an upgrade history record, navigate to System DiagnosticsUpgrade History and click the upgrade. Note: Debug Upgrade provides detailed debugging output for transactions containing artifacts affected by the most recent upgrade, and is designed to assist in upgrade error resolution. See [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."). Note: The Payload and Payload Hash fields have been removed from the Upgrade History record in a previous release. {#c_UpgradeHistory__table_zqk_sxn_1p__entry__2} | Field | Description | |-|-| | From | Name of the previous .war file (version). | | To | Name of the applied .war file (version). | | Upgrade started | Time stamp when the upgrade process began. | | Upgrade finished | Time stamp when the upgrade process was completed. | | Changes skipped | Total number of records that were different from the previous upgrade but were skipped, mostly likely due to customization. Changes skipped is the sum of the records that have disposition of skipped manual merge (where the value of changed is true), added to the number of records that have disposition of skipped error, added to the number of records that were skipped and different. Note: 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. One of your responsibilities as the administrator is to resolve each update that was skipped due to a customization. To resolve a skipped update, you review the reason for each skipped record and then either merge the customization or revert the customization to the base system. | | Changes applied | Total number of the changes that were applied in this upgrade. Changes applied is sum of updated and different records, added to the number of deleted records (where the value of changed is true) added to the number of inserted records (where the value of changed is true). | | Changes processed | Total number of items processed during this upgrade. Changes processed is the sum of Changes skipped, plus Changes applied. | [Table 1. Upgrade History record] {#c_UpgradeHistory__table_zqk_sxn_1p} {#c_UpgradeHistory__table_gfb_5jd_tbb__entry__2} | Field | Description | |-|-| | Updated and different | Number of Upgrade Detail records for which the value of the disposition is updated, and the value of changed is equal to true. This does not appear on the form by default. | | Updated and not different | Number of Upgrade Detail records for which the value of the disposition is updated, and the value of changed is equal to false. This does not appear on the form by default. | | Skipped and different | Number of Upgrade Detail records for which the value of the disposition is skipped, and the value of changed is equal to true. This does not appear on the form by default. | | Skipped and not different | Number of Upgrade Detail records for which the value of the disposition is skipped, and the value of changed is equal to false. This does not appear on the form by default. | [Table 2. Upgrade History Details form section] {#c_UpgradeHistory__table_gfb_5jd_tbb} ## Review Skipped Records form section 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.") displays each record that was skipped during the upgrade process. Use the list to review the reason for each skipped record in the list and then either merge your customization or revert your customization to the base system. * **[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. * **[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. * **[Customizations Unchanged related list](https://servicenow-prod.fluidtopics.net/0Rl0OK_cQ5c4icPXqqMC8w)** Customizations Unchanged lists all records that were skipped (due to a customization), but the changes that were going to be applied in this upgrade have not changed from the last upgrade. * **[Changes Applied related list](https://servicenow-prod.fluidtopics.net/N_vtEXgSCUVtijvwl3Z3jA)** Changes Applied lists all changes that were applied in this upgrade. * **[Claim Outcomes to Review related list](https://servicenow-prod.fluidtopics.net/WivJHclEp6W1t2qrpxt~9Q)** During system upgrades, the Claim Status tab displays outcomes to review and resolve. See the Claim Status field in the table below. * **[Upgrade Details related list](https://servicenow-prod.fluidtopics.net/xjIZ4oE_4aHzfoAY0fUsiQ)** Upgrade Details lists all Upgrade Details records for this upgrade. *[\>]: and then