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 determines whether new scan requests can be queued when another scan is currently running, impacting the handling of concurrent scans. |
| What area does it affect? |
Instance scanning |
| What does the default mean? |
The default value is "true", which means this behavior is enabled by default. |
| When should you review it? |
Review this property when configuring scan workflows or troubleshooting scan request rejections. |
Out of the box property record
Raw metadata from the property record.
| Property name |
glide.scan.queue.enabled |
| Sys ID |
55eb527cff202210a430ffffffffff96 |
| Type |
boolean |
| Application |
Global |
| Default value |
true |
| Description |
This property enables the queuing feature for instance scans. If this flag is set to false, queuing will be disabled, and any new scan requests will be rejected if another scan is already in progress. |
| Updated |
2025-03-25 05:40:46 |
Sources
Official references and nearby text excerpts where this property appears.
Context preview
Snippet 1
... and helps teams receive faster feedback when multiple scans are triggered across scripts, tables, update sets, or large code and configuration changes. Parallel scan uses a queue-based execution model when glide.scan.queue.enabled property is enabled. If queuing is enabled, the request is placed in the queue and later picked up for execution. If queuing is not enabled, the scan starts immediately when ...
Related properties