Scanning

Understanding Scan Statuses

What each scan status means and what actions are available at each stage.

Scan Lifecycle

Every scan passes through a series of statuses from creation to completion. Understanding these statuses helps you monitor progress and troubleshoot issues.

Status Definitions

`queued`

The scan has been submitted and is waiting in the queue. It will begin once a slot is available and any scans ahead of it have been dispatched. No action is required — you can cancel the scan while it is queued.

`pending_verification`

The scan was requested but the target's ownership verification has expired or was never completed. Verify the target to allow the scan to proceed.

`provisioning`

APVISO is setting up a secure, isolated environment for your scan. This typically takes 15–30 seconds.

`running`

The agents are actively testing the target. You will see real-time agent messages and findings streaming to the dashboard. Running scans have a maximum duration of 3 hours.

`completed`

The scan finished successfully. All findings have been saved and the final report has been generated.

`failed`

Something went wrong during the scan — for example, the target was unreachable or an internal error occurred. Partial results may be available. Check the scan log for error details. Failed scans do not consume credits.

`cancelled`

You manually cancelled the scan before it completed. Partial findings discovered before cancellation are preserved. Credits are refunded for cancelled scans.

Actions by Status

  • queued — cancel.
  • pending_verification — verify target, cancel.
  • provisioning — cancel.
  • running — watch live, cancel.
  • completed — view findings, download report, retest findings.
  • failed — view partial results, retry scan.
  • cancelled — view partial results, retry scan.

Timeout Behavior

If a scan reaches the 3-hour maximum, APVISO gracefully stops the agents, saves all findings discovered so far, generates a partial report, and marks the scan as completed with a timeout flag. You can run a follow-up scan to continue testing from where the previous one left off.