Running scans
Start a scan, follow its progress, attach to a running scan, cancel it, and review history.
Starting a scanPermalink to Starting a scan
Choose a repository in the Active state and start the scan. The scan is queued immediately and then works through its phases. You do not need to keep the page open.
Where this happens in the console
One scan per repository at a time
Progress phasesPermalink to Progress phases
A running scan reports one of five progress phases. They are ordered, and the console shows them as a stepper.
| Phase | What is happening |
|---|---|
| Queued | The scan is accepted and waiting to begin. |
| Preparing repository | The repository contents are being made ready for analysis. |
| Analyzing code | The analysis itself is running. |
| Validating findings | Candidate findings are being checked before they are reported. |
| Preparing report | The result is being assembled. |
A scan then reaches one of four terminal states: Complete, Failed, Canceled, or Needs review.
Attaching to a running scanPermalink to Attaching to a running scan
Open the repository or the scan from history and the console attaches to the run in progress, showing its current phase live. Closing the tab does not stop the scan.
CancellingPermalink to Cancelling
You can cancel a scan while it is running. A cancelled scan is reported as Scan canceled and produces no result — cancellation is not a failure, and it is not a clean result either.
Scan historyPermalink to Scan history
Every scan for the workspace is listed with its repository, when it ran and how it ended. Open any entry to read its result, including scans that failed or were cancelled.