Key questions about this property
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? |
This property configures the limit on concurrent transactions for the Script Debugger, allowing for efficient management of debugging sessions. |
| What area does it affect? |
Script Debugger |
| What does the default mean? |
No default value is stated in the ServiceNow documentation. |
| When should you review it? |
Review this property when adjusting debugging performance or managing multiple concurrent debugging sessions. |
Property record
Facts stated in the ServiceNow documentation. No out of the box record has been read from an instance yet.
| Property name |
glide.debugger.config.max_node_concurrency |
| Type |
Not stated |
| Application |
Not stated |
| Default value |
Not stated |
| Description |
Not stated |
Sources
Official references and nearby text excerpts where this property appears.
Context preview
Snippet 1
... 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 ...
More in glide (other)
Other properties in the same namespace.
All 457 properties in glide (other) →