---
title: Script Debugger multiple developer support
description: The Script Debugger allows multiple developers to debug their own transactions without affecting each other.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/api-reference/scripts/multiple-developer-support.html
release: australia
product: Scripts
classification: scripts
topic_type: concept
last_updated: "2026-03-12"
reading_time_minutes: 1
breadcrumb: [Script Debugger, Debugging scripts, Scripting, API implementation, API implementation and reference]
---

# Script Debugger multiple developer support

The Script Debugger allows multiple developers to debug their own transactions without affecting each other.

The Script Debugger only allows developers to see and interact with items related to their current debugging session such as:

-   Breakpoints
-   Call stack
-   Console
-   Transactions
-   Status

The Script Debugger prevents one developer from seeing or modifying another debug session. Administrators, however, can impersonate another user, open the Script Debugger, and debug transactions generated by the impersonated user.

The Script Debugger displays the debug session user at the bottom left of the user interface.

\[Omitted image "script-debugger-user.png"\] Alt text: The Script Debugger User field showing the sample admin user

## Concurrent Script Debugger usage

By default, the system supports debugging `[(The number of semaphores on the instance) / 4]` concurrent transactions. Administrators can specify the number of concurrent transactions the system can debug by setting the **glide.debugger.config.max\_node\_concurrency** system property. The system can debug up to `[(The number of semaphores on the instance) - 2]` concurrent transactions.

## Administration of debugging sessions

Debugging sessions can remain actively debugging \(in the EXECUTION\_PAUSED or WAITING\_FOR\_BREAKPOINT statuses\) until:

-   The user pauses the Script Debugger.
-   The user closes the Script Debugger.
-   The user session ends.

Administrators can view the currently running debugger sessions by navigating to the page `xmlstats.do`.

Administrators can stop all currently running debugging sessions by navigating to the page `debugger_reset.do`. Only users with the admin role can access this page.

**Parent Topic:**[Script Debugger and Session Log](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/scripts/script-debugger.md)

**Related topics**  


[Script Debugger impersonation support](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/scripts/impersonation-support.md)