---
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


---

# Debug upgrade

# Debug upgrade {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

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.
Administrators and technical personnel can use this output as an adjunct to the Upgrade History and Upgrade Monitor modules. Debug Upgrade is a component of standard ServiceNow session debugging. You enable Debug Upgrade, process a transaction (for example, load a form), then analyze the reported upgrade information. See .

## Reported debug information {#debug-upgrade__section_sww_txt_d2b}

Debug Upgrade includes several expandable sections:

* Skipped During Last Upgrade
* Customer Customized
* ServiceNow Modified During Last Upgrade

{#debug-upgrade__ul_aws_szt_d2b}These sections serve as a starting point for diagnosing when a function or artifact does not operate as expected after an upgrade. Each listing sorts by the dates the artifacts were processed, with the most recent appearing first. Expand the appropriate section, and click the name of a listed artifact to view the underlying artifact record. These records include update version history, which represents the state of a customizable object at specific times. See [Version records](https://www.servicenow.com/docs/access?context=r_VersionRecords&version=xanadu&pubname=xanadu-application-development&ft:locale=en-US).  
The listed artifacts may require some kind of possible user intervention or action. Using underlying artifact detail, you can determine:

* what artifacts have changed?
* what artifacts have not been changed that would or should have?
* what changed artifacts were missed?
* what artifacts operate differently than expected (if referencing something that has changed during last upgrade)?
{#debug-upgrade__ul_h3z_zvt_d2b}

Depending on the answers to these questions, you may have to modify the selected
artifact so it works in the way you expect. Conversely, you might simply accept the new
updates made to the artifact, and its changed functionality.

## Skipped during last upgrade {#debug-upgrade__section_fpj_xdd_ydb}

Lists artifact records that were skipped during the last upgrade that also ran during the
last transaction. These records are standard objects that missed changes from ServiceNow because they were modified at some point by a user. See [Resolve conflicts for an individual record](https://servicenow-prod.fluidtopics.net/TYHza6FgOPnDiwsVuD5Lag "Reconcile differences between your customized record and the changes associated with the upgrade.").

## Customer customized {#debug-upgrade__section_lgt_xdd_ydb}

Lists all artifact records that were customized at some point by users that also ran during
the last transaction. This listing is not strictly related to the actual activities
performed during the last upgrade session. The listing does include the records that appear
under Skipped During Last Upgrade. However, not all records that appear in the Customer
Customized list are included in Skipped During Last Upgrade.  
Note:  
Customizations that you designate for replacement during upgrades, by setting the Replace on Upgrade field in the customization record to true, do not appear on the Customer Customized section list. While this listing is not directly related to the activities performed during the last
upgrade, it may be worthwhile to look at individual customization records listed on it. Some
of the listed customization records may be referencing other records changed or skipped
during upgrade. The activities performed during the last upgrade may have an impact on, or
affect these relationships.

## ServiceNow modified during last upgrade {#debug-upgrade__section_ksv_xdd_ydb}

Lists all standard (non-customized) artifact records modified by ServiceNow during the last upgrade that also ran during the last
transaction.
* **[Enable and use debug upgrade](https://servicenow-prod.fluidtopics.net/Vog2SWAuGbRb8~5xo~IaQA)**   
  Enable Debug Upgrade to analyze post-upgrade issues that may require follow up, then disable it when finished with the upgrade debugging session.

**Related concepts**   

* [Upgrade History module: Track every upgrade](https://servicenow-prod.fluidtopics.net/K757RA2upV6i8hOwVbrzBw "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.")  
**Related reference**   

* [Upgrade Monitor module: Upgrade an individual instance](https://servicenow-prod.fluidtopics.net/PBGJUExg1J~DD0cmu5vigg "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.")