---
sourceDocument: Australia API Reference
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/api-reference

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia API Reference

ft:clusterId :

    - crapiref

bundleId :

    - crapiref

workflow :

    - Creator


---

# Script Tracer

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

Release version: Australia  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Script Tracer and debugging scripts

The Script Tracer in ServiceNow helps administrators efficiently debug scripts and business rules by filtering and narrowing down script execution details.
Available to users with the admin role, it can be accessed viaAll \> System Diagnostics \> Script Tracer.
Once enabled, it tracks script execution during a UI transaction, identifying lines of code and record changes, which saves time by avoiding broad searches.
Show full answer Show less  

## Key Features

* **Filters:** Limit tracing by file type or specific table to focus on relevant scripts.
* **Change Tracking:** Detects and lists changes to records during script execution.
* **State Tab:** Displays differences between old and new script states with an option to show only changed fields.
* **Error Display:** Shows errors with line numbers and messages in order of occurrence.
* **Script Viewing:** View complete lines of changed code and open scripts directly in Debugger or in the platform's editor.
* **Transaction Records:** Provides visibility into all transaction records related to the trace.
* **Trace Management:** Clear the trace when finished to start a new one.

## Trace Limits and Configuration

By default, the Script Tracer captures up to 1,000 lines of script per trace to avoid excessive data. After reaching this limit, you must clear the trace before starting a new one. Administrators can adjust this maximum line limit by setting the **glide.debug.trace.tracelinelimit** property according to their tracing needs.

## Practical Benefits for ServiceNow Customers

Using Script Tracer enables faster identification and resolution of script-related issues by focusing on specific files and tables, viewing exact code changes, and handling errors efficiently. This results in improved productivity and reduced debugging time, especially when managing complex scripts or business rules in your ServiceNow environment.  
The Script Tracer can help you filter your debugging search to quickly narrow down script problems. You can identify lines of code in a script and other changes to its record during execution. Finding those specific lines of
scripts rather than doing a wide search helps save time and improves productivity.

## Overview of Script Tracer {#script-tracer__section_qfn_mxg_knb}

Use the Script Tracer to narrow your search so you can debug scripts and business rules more efficiently. With the admin role, you can access Script Tracer by navigating to AllSystem DiagnosticsScript Tracer.

After 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 record during script execution and presents them in a list for you to examine. When you select Start Tracer, the Tracer begins searching for changes in the
record. You can select 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 to the record aren't 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 code that the record has undergone during execution. You can view the entire line of script by selecting 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're 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. After 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/yrUVyiUnIfGofpZ_SzTuPA "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.").

*[\>]: and then