Script Tracer and debugging scripts
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
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 All > System Diagnostics > Script 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
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.[Omitted image "script-tracer-diff-line.png"] Alt text: Script difference output
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.
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.
Limiting the tracer
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.
Parent Topic:Script Debugger user interface
--- title: Script Tracer and debugging scripts description: 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. locale: en-US canonical_url: https://www.servicenow.com/docs/r/api-reference/scripts/script-tracer.html release: brazil product: Scripts classification: scripts topic_type: concept last_updated: "2026-09-10" reading_time_minutes: 2 breadcrumb: [Script Debugger user interface, Use Script Debugger, Debug scripts, Scripting, API implementation, API implementation and reference] --- # Script Tracer and debugging scripts 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 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 **All** > **System Diagnostics** > **Script 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 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.\[Omitted image "script-tracer-diff-line.png"\] Alt text: Script difference output 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. **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. ## Limiting the tracer 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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/scripts/script-debug-overview.md). **Parent Topic:**[Script Debugger user interface](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/scripts/parts-script-debugger-interface.md)
| title | Script Tracer and debugging scripts |
| description | 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. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/api-reference/scripts/script-tracer.html |
| release | brazil |
| product | Scripts |
| classification | scripts |
| topic_type | concept |
| last_updated | 2026-09-10 |
| reading_time_minutes | 2 |
| breadcrumb | Script Debugger user interfaceUse Script DebuggerDebug scriptsScriptingAPI implementationAPI implementation and reference |