--- 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 module # Upgrade Monitor module {#ariaid-title1} * Release version: Xanadu * * Updated August 1, 2024 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Schedule an upgrade and monitor the status of an ongoing upgrade using the Upgrade Monitor module. You can also view the upgrade summary and the list of records causing conflicts in your instance once the upgrade is complete. ## Access Upgrade Monitor {#uc-monitor-module__section_yzj_hfh_plb} 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 AllUpgrade CenterUpgrade Monitor. ## How the Upgrade Monitor fits into the upgrade process {#uc-monitor-module__section_wyk_qfh_plb} Note: For detailed information about the upgrade process, see [Upgrade your instance](https://staging-docs-servicenow.zoominsoftware.io/bundle/vancouver-release-notes/page/release-notes/upgrades/concept/upgrades-overview.html). 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 list](https://servicenow-prod.fluidtopics.net/EMskfIj~XY3DAygS2Sf3~w "Process the skipped records list to resolve the differences between the upgraded and customized versions of a record. If you have customized or altered a record affected by this upgrade, such as a business rule or script, the upgrade generates a skip log record."). 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. {#uc-monitor-module__ol_dny_3gh_plb} 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 might take on the production instance Note: [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.") provides detailed debugging output for transactions containing artifacts affected by the most recent upgrade, and is designed to assist in upgrade error resolution. {#uc-monitor-module__ul_fmj_4gh_plb} ## Monitoring an individual instance as it upgrades {#uc-monitor-module__section_adg_1hh_plb} While the upgrade is in progress the Upgrade Progress 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. The Upgrade Summary Report provides information about conflicts between customizations versus changes in the upgrade and provides a link to reconcile these conflicts. For information about understanding and resolving these conflicts, see [Process the skipped records](https://servicenow-prod.fluidtopics.net/EMskfIj~XY3DAygS2Sf3~w "Process the skipped records list to resolve the differences between the upgraded and customized versions of a record. If you have customized or altered a record affected by this upgrade, such as a business rule or script, the upgrade generates a skip log record.") list. When you upgrade a non-production instance, the Upgrade Summary Report can help you estimate how long the same upgrade might take on a production instance. For details about the elements on this report and how to use this information, see [Upgrade Details form](https://servicenow-prod.fluidtopics.net/pmaZ6ZaESBLhY_Oipgy13g "From the Upgrade Details form, you can review an individual record affected by the upgrade and reconcile conflicts between the upgrade and customizations."). ## Resolving conflicts {#uc-monitor-module__section_ll5_dhh_plb} 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 and resolve these conflicts. The system records the changes you make during this process in update sets. See [Review skipped records using related lists](https://servicenow-prod.fluidtopics.net/HFoFAheZCumIuyFcCuopBg#uc-access-rl "Use different related lists to resolve, track and review the skipped records in an upgrade."), for more information. 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/EMskfIj~XY3DAygS2Sf3~w "Process the skipped records list to resolve the differences between the upgraded and customized versions of a record. If you have customized or altered a record affected by this upgrade, such as a business rule or script, the upgrade generates a skip log record."). *[\>]: and then