Scan: Queued

A Queued Run has been submitted and accepted, but no worker has started processing it yet. The Status badge shows Queued in grey, the Duration reports the time spent waiting (for example, Queued for 45 seconds), and the progress bar and summary counters read zero because no containers have been picked up. This is the normal first state for a Scan: the Run stays Queued until a worker is free to begin, then it transitions to Running. When processing capacity is full, the Run stays visibly Queued instead of appearing to run. The only action available while Queued is Abort.

Expanded row in the operations list

Header of the operation

No.	Element	What it shows
1	Operation ID and type	The unique identifier (for example `#53201`) and the operation type (Scan). The icon next to the ID links to the dedicated Overview of the operation.
2	Status badge	The grey Queued badge indicating the Run is waiting to be picked up.
3	Time info	Started At records when the Run was submitted, and Duration reports the time spent waiting (for example, `Queued for 45 seconds`).
4	Progress	The progress bar shows `0` while Queued: no containers have been picked up yet. It begins advancing once the Run transitions to Running.
5	Triggered by	The user (avatar and name) who launched the operation, or the schedule that fired it.
6	Schedule	The named schedule if recurring, otherwise `No schedule`.
7	Quick stats icons	The result counters (Anomalies Identified, Anomalies Auto-Resolved) read zero (the Anomalies tooltip shows `No anomalies`) because the Run has not produced any data yet. Configuration icons (Incremental Field, Remediation Strategy) still reflect the settings the Run will execute with.

The grey Queued badge confirms the Run is waiting: nothing is being processed yet, and the only action available is Abort.

Details of the operation

Expanding the row reveals the Settings the Run will execute with (read-only) and the Abort action.

No.	Setting	What it shows
1	Check Categories	Which categories the Run will execute.
2	Incremental	Read strategy that will be used (Enabled/Disabled).
3	Read Record Limit	Per-container record cap.
4	Archive Duplicate Anomalies	Setting from Step 4.
5	Reactivate Recurring Anomalies	Setting from Step 4.
6	Auto Resolve Anomalies	Setting from Step 4 (Full scans only).
7	Maximum Record Anomalies per Check	The rollup threshold in effect.
8	Maximum Source Examples per Anomaly	Source examples cap in effect.
9	Remediation Strategy	The remediation strategy in effect.
10	Abort	The only action available while Queued. Cancels the Run before it starts; the row transitions to the Aborted state with an `Operation Aborted by <user>` event in the Timeline. Because the Run has not started, aborting a Queued Run leaves no partial results behind.

The settings are shown for reference only. They cannot be edited once the Run is submitted; to change them, abort the Run and start a new one.

Summary

The Summary block renders while the Run is Queued, but every counter reads zero: Tables Scanned, Partitions Scanned, Records Scanned, and Anomalies Identified all show 0 (Tables Requested reflects the total targeted). The counters begin updating once a worker starts processing and the Run moves to Running.

Operation detail page

Clicking the row opens the dedicated operation detail page. While Queued, the Run carries its identity and settings, its metrics all read zero, and the Timeline shows the run's first entry, but there are no per-container results yet.

Overview tab

Operation block

No.	Element	What it shows
1	Status	The state badge (Queued, grey).
2	Started At	Timestamp the Run was submitted.
3	Duration	Time spent waiting so far, ticking up live (for example, `Queued for 45 seconds`).
4	Progress	Shows `0` while Queued; no containers have been processed. Advances once the Run transitions to Running.
5	Triggered By	User who launched the operation, or schedule.
6	Schedule	The named schedule (or `No schedule`).
7	Remediation Strategy	Effective remediation strategy for the Run.

Settings block

The Settings block lists the scan settings the Run will execute with (same fields as the row's Details section, minus the Abort action).

Summary block

The Summary block renders while Queued with every metric at zero. The counters start updating once the Run transitions to Running and containers begin completing.

Timeline block

While Queued, the Timeline shows an Operation In Progress entry with the subtitle Queued..., alongside the Operation Started entry stamped with the submission time. There is no separate "Operation Queued" event: the Queued... subtitle on the In Progress entry is what marks the waiting state. Once a worker picks the Run up, the subtitle changes to Running... and the badge changes to Running.

Results tab

The Results tab is empty while Queued. No containers have been processed, so there are no rows to list yet.