Skip to content

Scan Queue

The Scan Queue page provides real-time visibility into your organization's scanning activity. Monitor running scans, track queued requests, and manage capacity across your scan pipeline.

Accessing the Scan Queue

Navigate to Scan Queue from the left sidebar. The page displays four sections:

  1. Capacity overview cards
  2. Running scans with progress indicators
  3. Queued scans waiting for capacity
  4. Recent scan history

Capacity Cards

At the top of the Scan Queue page, four summary cards provide an at-a-glance view of your scanning capacity:

Card What It Shows Example
Scanners Available The number of scanner slots not currently in use 2 of 3 available
Running The number of scans currently executing 1 running
In Queue The number of scans waiting for a free scanner slot 4 in queue
Max Duration The maximum allowed duration per scan on your plan 30 minutes

Capacity by Plan

Your plan tier determines your concurrent scan capacity:

Plan Max Concurrent Max Queue Depth Max Duration
Free 1 5 10 minutes
Pro 3 20 30 minutes
Enterprise 10 100 60 minutes

The capacity cards update in real time. When a running scan completes, the next queued scan begins automatically and the cards reflect the new state.

Running Scans

The Running Scans section displays each scan that is currently executing:

Scan Card Layout

Each running scan is displayed as a card with the following information:

┌─────────────────────────────────────────────────────────┐
│  org/repo-name                                          │
│  Scanner: OpenGrep  •  Branch: main  •  Rule Set: Default│
│                                                         │
│  ████████████████░░░░░░░░░░  2m 34s elapsed            │
│                                                         │
│  Started: 2026-04-15 14:23:01 UTC                       │
└─────────────────────────────────────────────────────────┘
Field Description
Repository The asset being scanned
Scanner Which scanner is running (OpenGrep, Semgrep, Trivy, Grype, Gitleaks)
Branch The branch being scanned
Rule Set The rule set selected for this scan
Progress Bar Visual indicator of elapsed time relative to max duration
Elapsed Time How long the scan has been running
Started The UTC timestamp when execution began

Progress Indicator

The progress bar shows elapsed time as a proportion of the maximum scan duration for your plan. It does not indicate percentage of code scanned, since scan completion is not predictable in advance.

Queued Scans

The Queued Scans section displays scans waiting for scanner capacity in a table format:

Column Description
Position Queue position (1 = next to run)
Repository The asset to be scanned
Scanner Which scanner will be used
Branch Target branch
Queued At When the scan was submitted
Queued By Who triggered the scan (user email or "Scheduled" for nightly scans)
Cancel A button to remove the scan from the queue

Queue Order

Scans are processed first-in-first-out (FIFO). The scan at position 1 will be the next to start when a scanner slot becomes available.

Queue Depth Limits

If the queue is full (at your plan's maximum depth), new scan requests will be rejected with an error:

Scan queue is full. Please wait for existing scans to complete.

Either wait for scans to complete or cancel queued scans you no longer need.

Cancelling a Queued Scan

Click the Cancel button on any queued scan to remove it from the queue. Cancelled scans:

  • Are removed immediately from the queue
  • Do not consume any scan quota
  • Are recorded in scan history with status "Cancelled"
  • Free up queue depth for new scan requests

Running Scans Cannot Be Cancelled

Once a scan transitions from Queued to Running, it cannot be cancelled from the UI. Running scans will complete or fail based on their execution.

Recent Scan History

Below the active sections, a table shows recently completed scans:

Column Description
Repository The asset that was scanned
Scanner Which scanner was used
Status Completed, Failed, or Cancelled
Duration How long the scan took
Findings Number of findings produced
Completed At When the scan finished

Click any row to view the full scan details and findings.

Tier Limits in Detail

Free Tier

Limit Value
Concurrent scans 1
Queue depth 5
Max scan duration 10 minutes
Scheduled scans Not included

The Free tier allows one scan at a time with a small queue. Ideal for individual developers evaluating the platform.

Pro Tier

Limit Value
Concurrent scans 3
Queue depth 20
Max scan duration 30 minutes
Scheduled scans Included (nightly)

The Pro tier provides enough capacity for small-to-medium teams running regular scans across dozens of repositories.

Enterprise Tier

Limit Value
Concurrent scans 10
Queue depth 100
Max scan duration 60 minutes
Scheduled scans Included (nightly + custom schedules)

The Enterprise tier is designed for large organizations with hundreds of repositories and continuous scanning requirements.

Need More Capacity?

If you are consistently hitting queue limits, consider upgrading your plan. Enterprise customers can also request custom capacity allocations. Contact support at support@mayoaspm.com.

Monitoring Tips

During Scheduled Scans

The nightly scheduled scan pipeline (3:00 AM UTC) may queue many scans at once. During this window:

  • Expect the queue to fill up and drain over 1-3 hours
  • Queued scans show "Scheduled" as the trigger source
  • Ad-hoc scans submitted during the nightly window will queue behind scheduled scans

After Triggering Bulk Scans

If you trigger scans on many assets in quick succession:

  1. Check the Scan Queue page to confirm they are queued
  2. Monitor the Running section for progress
  3. Watch for any failures in the Recent History section

Identifying Slow Scans

If a scan's elapsed time is approaching the max duration:

  • The progress bar will be nearly full
  • Large repositories with comprehensive rule sets take longer
  • Consider using a targeted rule set (e.g., "Critical + High Only") for very large repos

Next Steps