--- 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 Monitor overview # Upgrade Monitor overview {#ariaid-title1} * Release version: Xanadu * * Updated August 1, 2024 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read The Upgrade Monitor helps you upgrade an individual instance. You can monitor the progress of an upgrade and resolve conflicts between the upgrade and customizations.{#platform-upgrades__lcj_jhs_kx} ## Set up for the Upgrade Monitor In Xanadu, the Upgrade Monitor is installed by default.{#platform-upgrades__uwd_mx5_jx} If you log in with the admin role while an upgrade is underway, the system automatically displays the Upgrade Progress screen. If no upgrade is in progress, you can navigate to System DiagnosticsUpgrade Monitor.{#platform-upgrades__y5t_pkg_jx} ## How the Upgrade Monitor fits into the upgrade process {#platform-upgrades__zhl_bhy_dx} Note: For detailed information about the upgrade process, see [Upgrade your instance](https://www.servicenow.com/docs/access?context=upgrades-overview&version=xanadu&pubname=xanadu-release-notes&ft:locale=en-US). The Upgrade Monitor concerns only part of the larger upgrade process: 1. Clone the production instance to a test instance and a non-production instance. 2. Apply the upgrade to the non-production instance. 3. On the upgraded non-production instance, [Process the skipped records list](https://servicenow-prod.fluidtopics.net/AsV6nqTAf652imq_iRnB6w "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.") 4. Test the non-production instance to confirm that the instance still works and performs adequately. Compare to benchmark data from pre-upgrade production instance. 5. Apply the upgrade to the test instance. Import the update sets created on the non-production instance when you processed the skipped list. Repeat the testing to make sure that the process is working. 6. Apply the upgrade to the production instance. Import the update sets created on the non-production instance when you processed the skipped list. Test to confirm that the instance works and performs adequately. {#platform-upgrades__hsh_b5x_dx} Within this larger process, the Upgrade Monitor helps you upgrade individual instances: * during the upgrade, it shows where in the process the system is * after the upgrade, it reports what the upgrade did and for how long * as you upgrade the first non-production instance, it helps you resolve conflicts between customizations and changes that are part of the upgrade * on non-production instances, it provides information that can help you estimate how long the upgrade takes on the production instance. {#platform-upgrades__m2x_kdr_kx} 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."). ## Monitoring an individual instance as it upgrades While the upgrade is in progress 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.") shows what the upgrade process has done, what it is doing, and what remains to be done. When the upgrade completes, 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."). The Upgrade Summary Report provides information about conflicts between customizations versus the upgrade and provides a link to reconcile these conflicts. For information about understanding and resolving these conflicts, see [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."). When you upgrade a non-production instance, the Upgrade Summary Report can help you estimate how long the same upgrade takes on a production instance. For details about the elements on this report and how to use this information, see [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."). ## Resolving conflicts {#platform-upgrades__h3l_bhy_dx} To prevent losing customizations, the system skips upgrading records you have customized and provides you with a list of these skipped records. As you upgrade your first non-production instance, go through 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.") and resolve these conflicts. The system records the changes you make during this process in update sets. You do not need to reconcile the skipped list on any instances you later upgrade. Instead, you can apply the upgrade then import the update sets containing your changes. For details on reconciling conflicts, see [Process the skipped records list](https://servicenow-prod.fluidtopics.net/AsV6nqTAf652imq_iRnB6w "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."). *[\>]: and then