ScanlyAppScanlyApp
Run A Scan
Home/Docs/Runs

Runs

Runs record a scan execution with status, coverage, performance metrics, issue detections, and artifacts.

Why it matters

Runs are your source of truth for release readiness.
Every issue, performance score, and artifact is tied to a run.

Step-by-step

  1. Open a project and start a scan.
  2. Monitor status in Scan History.
  3. Open the run details page.
  4. Review executive metrics and issue summary.
  5. Expand issue rows for evidence.
  6. Open trace replay when deep debugging is required.

Run states

  • queued -> waiting for worker
  • running -> scan in progress
  • passed / failed -> completed state

Visual reference

Scan report view

Common mistakes

  • Treating a passed run as "no issues"; it only means execution succeeded.
  • Ignoring regressions between current and previous runs.
  • Exporting reports before run completion.

Related docs