Scan Status
Understanding Secbez scan status indicators — pending, running, completed, and failed states.
Status values
| Status | Meaning |
|---|---|
| Pending | Scan has been queued and is waiting to start |
| Running | Scan is actively analyzing your code |
| Completed | Scan finished successfully with all findings processed |
| Completed with errors | Scan finished but some analysis steps encountered issues. Findings are still valid — some may have reduced context. |
| Failed | Scan could not complete. This usually indicates a configuration or connectivity issue. |
Completed vs. Completed with errors
A completed scan ran all detection and validation steps without issues.
A completed with errors scan still produces valid findings, but some non-critical steps may have been skipped or timed out. Common causes:
- An AI validation step timed out for some findings (those findings are flagged for manual review instead of being auto-validated)
- The code graph was unavailable (findings are still produced but without cross-file context)
In both cases, no findings are silently dropped. If a step fails, the affected findings are preserved and marked for review.
GitHub Check Run status
The GitHub Check Run status maps to your configured policy:
| Check status | Meaning |
|---|---|
| Pass | No findings exceeded your policy thresholds |
| Warning | Some findings exceeded warning thresholds but not failure thresholds |
| Fail | One or more findings exceeded your failure policy thresholds |