Scan Center
"Did the scan run?" is a surprisingly hard question to answer in most security tools, and "why is it still waiting?" is harder. Scan Center answers both, because everything Dwaar does to your resources passes through one queue.
You rarely need to start anything here. Discovery plans the work. Come here to see it, and to step in when something is stuck.
Prerequisites
scans:readto see the queue.- A connected integration. Without one, discovery has nothing to do. See Integrations.
The queue
Open Scan Center. The Queue tab has three views, in the order work flows:
| View | What it shows |
|---|---|
| Upcoming | The next discovery of every connection, its frequency and its last run |
| Running | Discovery and scans that are running or waiting. This is the default view |
| History | Everything that finished: what each discovery found, and each scan's analyzers |
Scan Center also has Scanners, where you choose what runs, and Configurations, where you ignore findings.
Discovery drives scanning
There's no scan schedule to configure, and that's the part worth remembering. A connection's discovery frequency, hourly, daily or weekly, is the only schedule. Each discovery lists what the connection holds and plans runs per tracked ref:
- A snapshot that was never fully scanned gets a full scan.
- A snapshot that hasn't changed gets a vulnerability re-check.
You choose which of those happen on the connection's Scanning tab. See How discovery and scans work.
On Upcoming, select Run now to run a connection's discovery immediately. If the connection is in error, you'll see Fix instead, which takes you to the connection.
What a run is
A run is one scan of one snapshot: a commit of a tracked branch or tag, or an image index or manifest of a tracked image tag. It has a mode, a stage and a list of analyzers, one per enabled scanner.
Modes
| Mode | What it does |
|---|---|
| Full scan | Runs every enabled scanner on the snapshot |
| Vulnerability re-check | Only matches the last full scan's SBOM against current vulnerability data, so it finds what's newly disclosed without running the scanners |
| Posture check | Checks a connection's organization settings, AWS account, Vercel team, Railway workspace or Cloudflare account. It has no resource |
Stages
The Status groups these: every stage between queued and the end counts as running. A run finishes as completed, failed or cancelled.
Triggers
| Trigger | Label | What started it |
|---|---|---|
discovery | Discovery | Discovery found a new or changed snapshot |
schedule | Scheduled | Discovery re-checked an unchanged snapshot |
manual | Rescan | Someone selected Rescan or Force rescan |
one_time | One-time | Someone ran a one-time scan |
Analyzer status
Open a run to see each analyzer. Skipped means it doesn't apply to the snapshot or never ran. Cached means Dwaar reused a result from an earlier identical scan, which is why a run can finish faster than you expected. Neither is a failure.
Why a run is waiting
Your tenant has a limit on how many scans run at once. When it's reached, a queued run says so, naming how many scans are running and what the limit is. Nothing is wrong. It starts when a slot opens.
To move a waiting run up, change its priority in the Running view to Low, Normal or High. That needs scans:update and only works while the run is queued. Rescans and one-time scans already go in at high priority.
Try this next
Open History and look for a failed run. Read its error, then select Retry. Knowing what a failure looks like before one matters is the best use of ten quiet minutes.