Parallel scans

  • Release version: Australia
  • Updated March 12, 2026
  • 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

    • 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.
    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 for more information.