---
sourceDocument: Xanadu Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/application-development

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Script Tracer and debugging scripts

# Script Tracer and debugging scripts {#ariaid-title1}

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

The Script Tracer can help you filter your debugging search to quickly narrow down
script problems. You can identify lines of scripts in the Glide record that have undergone change
during execution. Finding those specific lines of scripts rather than doing a wide search helps
save time and improves productivity.

## Overview {#script-tracer__section_qfn_mxg_knb}

Use the Script Tracer to narrow your search so you can debug scripts and business rules more efficiently. You can find the Script Tracer by searching in the left navigation pane.  
Note:  
To use the Script Tracer, your role must be admin.  

|-|-|
|   |   |
[ ]

{#script-tracer__table_s5h_xzm_knb}Once you enable Script Tracer and execute a UI transaction, the Tracer searches through all the scripts being executed. The following filters are available:  
* File type: Search for a specific file type
* Table: Look in the specific table for the script being executed
{#script-tracer__ul_vhk_qsp_pnb}

The Script Tracer searches for changes in the script during execution and presents them in a
list for you to examine. When you click Start Tracer, the Tracer begins
searching for changes in the Glide record. You can click the Debug Script
button at any time to see the script itself.

Use the tabs to see specific information from the Tracer.  
The State tab displays the differences between the old and new scripts.

* By default, the Show only changed values check box is enabled, so you can avoid fields that have not changed.
* To view all the fields (changed or not), you can clear that check box.
{#script-tracer__ul_exv_ctp_pnb}  
Note:  
If the file is not reflected in the trace statement, it means the changes in the Glide record is not recognized by the system.

If there are any errors, they display at the top of
the State tab, with their line numbers and error message displayed in order of
occurrence.

* Script: Displays the line of changed scripts that the Glide record has undergone during execution. You can view the entire line of script by clicking the Show Script button.
* Transaction: Shows all transaction records of the trace
* Debug Script: Opens the script in Debugger to debug the script
* View File: Opens the script in the ServiceNow platform for editing
* Clear trace: Clears the trace when you are finished.
{#script-tracer__ul_a31_btp_pnb}

## Limiting the tracer {#script-tracer__section_eh5_dgv_pnb}

You may want to set a limit for your trace so that you don't generate too many returns. By
default there will be up to 1,000 lines of script traced. Once this number is reached you must
clear the trace and start tracing again. If you want to change the maximum number of lines for
tracing you can configure your limit using the property
glide.debug.trace.trace_line_limit.

Since each trace you run is new, make sure you're finished reading the results of one trace
before clearing it and beginning another one.

To learn more, see [Debugging scripts](https://www.servicenow.com/docs/S5iqqy8QkgKD_CQTAxOoOQ "Debug scripts using session logs and ServiceNow AI Platform debugging tools such as a walk-through script debugger and error messages that display in the UI.").