Reference C: Scan health values

Scan health indicates whether all scanners completed execution during a scan. Scan health applies to branch periodic scans, CI scans, and pull request scans.

Scan health	Probable cause	Coverage consequence	Next action
Completed	Every scanner completed execution.	Results are complete for every enabled scanner. A zero count for a scanner category is a genuine clean result for that category	Investigate the issues produced by the scan. Confirm that the enabled scanner set matches the intended coverage for the repository
Partially (completed)	One or more scanners failed or were skipped while others succeeded — for example, the IaC scanner succeeded and the Secrets scanner failed.	Results are absent, not clean, for the scanner that did not complete. Because the scan record reports detections rather than per-scanner execution, treat every enabled scanner on the repository as unverified	Diagnose the cause in the data source instance health view, correct the cause, then rescan. Do not treat any category count from this scan as a clean result
Error	The scan failed to complete. Common causes are a revoked or expired token, missing repository permissions, a clone failure, or a connection failure to the VCS provider.	No results are available for the repository for this cycle. The repository is unassessed	Diagnose the cause in the data source instance health view, correct the cause, then rescan
In Progress	The scan is currently executing.	Results are not yet final and are subject to change when the scan completes	Take no action. The Rescan action is not available while a scan is in progress

Note: The Rescan action is available only for a branch periodic scan with a scan health of Error or Partially (completed), and requires the app_sec_scans_periodic_edit permission.