---
sourceDocument: Australia ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/platform-administration

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Parallel scans

# Parallel scans {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Parallel scan is a functionality in Instance Scan that allows multiple scans to run in parallel instead of sequential execution. This improves efficiency and reduces wait times when several scans are executed concurrently.

Use parallel scan to reduce wait times and improve throughput when multiple scans are triggered at the same time. Parallel execution is especially useful in environments with large development teams or frequent scans, where running
scans sequentially can delay feedback and slow development and validation workflows. By enabling concurrent execution, parallel scan reduces delays caused by sequential processing 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 selected.  
Note:  
Scans can run in parallel only when both queuing and parallel scan properties are enabled.

## System properties for parallel scan {#hs-parallel-scan__section_uk2_hhb_b3c}

* glide.scan.parallel_scan_enabled: This property enables or disables parallel scan execution for Instance Scan. The default value for this property is `true`, allowing multiple scan requests to execute concurrently, subject to the configured maximum parallel scan limit. If set to `false`, scans run sequentially, even if queuing is enabled.

  For example, if the maximum parallel scan value is configured as 5, the first five scans are executed simultaneously. Any subsequent scans are added
  to a queue and run after the initial scans complete.
* glide.scan.queue.enabled: This property controls whether Instance Scan uses the queue-based execution model. The default value is `true` allowing scan requests to be sent to NowMQ and processed through the queue. This property must be enabled to allow scans to run in parallel, as queued execution is required for concurrent processing. When disabled, scan execution starts immediately when a scan is selected, bypassing the queue.
* glide.scan.max_parallel_scans: This property defines the maximum number of instance scans that can run concurrently. The default value for parallel scan limit is 5, with a supported minimum value of 1 and a maximum value of 15.

{#hs-parallel-scan__ul_u5v_3hb_b3c}  
Note:  
Parallel scan is applicable on full scan, test scan, suite scan, and reactive scan. It is not applicable with point scan.

See [Instance Scan properties](https://servicenow-prod.fluidtopics.net/XQcHg~VbMx0jf21jzi92dw "On the properties form, you can set parameters that control how the instance executes.") for more information.
**Related concepts**   

* [Executing a scan](https://servicenow-prod.fluidtopics.net/q69X8ioER7e5OOY~6WXJgw "Use the following types of scans to execute checks, a scan or a suite scan.")  
**Related tasks**   

* [Create a check](https://servicenow-prod.fluidtopics.net/pxMZytg88S33TLnKJJFVlw "Create your own checks by implementing the following procedure.")
* [Create a check suite](https://servicenow-prod.fluidtopics.net/O_mO72gOZTePbgLTQCguaA "Create a check suite to bundle a group of checks into a suite and execute it.")
* [Schedule a full scan](https://servicenow-prod.fluidtopics.net/UEHvpt8_aZqMpTy0WrsrVg "Create a schedule to regularly trigger a full scan even when you don’t have an active session. A schedule creates an established baseline for the health of the instance and provides a comparison to configuration and instance health over time.")
* [Schedule a suite scan](https://servicenow-prod.fluidtopics.net/O7gMmHVl7LngVs2SJWtRAw "Create a schedule to regularly trigger a suite scan even when you don’t have an active session.")
* [Monitoring a scan](https://servicenow-prod.fluidtopics.net/9lo69PkgffXYiR7CeBTaPw "You can check the progress status of a scan by checking the progress tracker.")
* [Queue your scan](https://servicenow-prod.fluidtopics.net/k2i9ZtSGJ640GIAje4_Llg "Leverage the scan queue feature to line up your scans for automatic execution following the current scan.")
* [Cancel a scan](https://servicenow-prod.fluidtopics.net/NUZdTo8tWpWO4IA4UzZaEA "Cancel or abort an ongoing scan by either selecting Cancel Scan in the scan execution modal or the Cancel Scan related link in the results record.")
* [Using the Instance Scan dashboard](https://servicenow-prod.fluidtopics.net/4HFuKt47kqEQ5E4kBxsgOQ "Compare and analyze the results of the scans in your instance by representing it on the premium Performance Analytics (PA) dashboard.")  
**Related reference**   

* [Reviewing of scans](https://servicenow-prod.fluidtopics.net/v2aWykUKyT5ovzK0Z~Bb9g "After the scans have been executed, you can review them with the findings and results components.")