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


---

# Transaction call chains

# Transaction call chains {#ariaid-title1}

* Release version: Xanadu
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Identify and debug the root causes for a problematic transaction by recording, and then reviewing, its call chain. A call chain consists shows the ordered series of scripts executed during the life cycle of a
transaction.

With Transaction Call Chain tracking, an administrator can register the URL of a problematic transaction. The call chain is then recorded during the next occurrence of the registered URL. Transaction call chains can help diagnose
transaction performance issues.

The following shows the workflow for enabling and using transaction call chain tracking.

1. When you find a problematic transaction on the Transaction Log or Slow Transaction list that requires debugging, select it to view its detail record. To aid in debugging, filter and group these lists by application scope, limiting transactions that appear to only those transactions originating in specific scopes.  
   Note:  
   To learn more about these lists, see [Transaction logs](https://www.servicenow.com/docs/access?context=r_TransactionLogs&version=xanadu&pubname=xanadu-platform-security&ft:locale=en-US) and [Slow transactions log record detail](https://servicenow-prod.fluidtopics.net/6hUeO9lVI_y~QAsvQsWsSQ "As an administrator, you can use Slow Transactions logs to gain insight into how transactions are affecting platform performance. To aid in debugging, you can filter transaction log detail by application scope, limiting transactions to only those transactions originating in specific scopes.").
2. In the record detail form, select Record call chain of next occurrence. Doing this designates that the next occurrence of the transaction URL should be persisted with all of its call chain information.

   Optionally, you can designate a user ID so call chain recording only takes place during the next transaction occurrence for a specific user.
3. The next time a user accesses the URL, the Transaction Call Chain Register record is updated to contain a list of the script resources executed to service the request. This list of resources is available for administrators to view by navigating to the Transaction Call Chain Record and selecting the Transaction Call Chain Related List.

4. In Transaction Call Chains, review the recorded call chain for the transaction, and then take the needed actions required to debug it.
{#transaction-call-chains__ol_vnx_2lh_f4b}
* **[Create a transaction call chain register](https://servicenow-prod.fluidtopics.net/0aChnHNLKoivFCHoHW9I6A)**   
  Create a call chain register to record call chain information for a problematic (or slow) transaction during the next occurrence of that URL. You specify that the next occurrence of the transaction URL should be persisted with all of its call chain information.
* **[Review a transaction call chain](https://servicenow-prod.fluidtopics.net/KFZgd77klb5u95EWvb8iyA)**   
  Use Transaction Call Chains to review the resulting call chain for a selected transaction. You can use the information in Transaction Call Chains can help debug performance issues.