Domains and scanning
Understand scan states
What queued, running, completed, and failed mean in the product.
- Audience
- All workspace members
- Plan availability
- All plans
- Last reviewed
Cyber Health Score processes scans asynchronously. The status labels in the product tell you where a scan is in its lifecycle.
Common scan states
| State | Meaning |
|---|---|
| Queued | The scan request was accepted and is waiting to be processed |
| Running | The scan is in progress |
| Completed | The scan finished successfully; findings and score output should be available |
| Failed | The scan did not complete successfully; review the message and retry when eligible |
| Cancelled | The scan was cancelled before completion |
What to expect
A brief gap between Queued and Running is normal. The product queues work rather than blocking the browser while checks run.
After Completed:
- refresh the posture or findings view if results do not appear immediately
- open Findings to review individual issues
Manual and scheduled scans
You can queue scans manually from asset workflows. Admin and Owner roles can configure scheduled rescans on supported plans.
Troubleshooting
| Situation | Recommended action |
|---|---|
| Queued for longer than expected | Wait and refresh; check plan limits |
| Failed scan | Confirm the asset is still verified and retry |
| Completed but sparse results | Some clean assets produce fewer findings; review all findings and report views |
Related documentation
Related documentation
Return to the documentation home to browse all topics.
Back to documentation