glide.session.max.concurrent.transactionsThe glide.session.max.concurrent.transactions property sets the limit on the number of concurrent transactions allowed per HTTP session. Admins should review this setting to ensure optimal performance and avoid potential session overload issues.
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? | This property defines the maximum number of concurrent transactions that can be processed in a single HTTP session, impacting system performance and user experience. |
|---|---|
| What area does it affect? | Session Management |
| What does the default mean? | The default value is "1", which sets the baseline numeric behavior for this property. |
| When should you review it? | Review this property when adjusting session handling or troubleshooting performance issues. |
Raw metadata from the property record.
| Property name | glide.session.max.concurrent.transactions |
|---|---|
| Sys ID | 2cb49df09f1013005cf3ffa4677fcf5a |
| Type | integer |
| Application | Global |
| Default value | 1 |
| Description | PLEASE CONTACT DEV-INTERFACES TEAM BEFORE CHANGING. More info at KB0683357 Determines the number of concurrent transactions can be executed per http session. |
| Updated | 2024-05-25 03:38:56 |