Understanding Scan Status and Job States
Overview
This guide explains how scan statuses are calculated and how individual job results affect the overall scan outcome. You will learn how to interpret status indicators, identify failed jobs, and understand parallel job execution across different scan types.
Prerequisites
- At least one scan created and executed
- Access to the scan dashboard
Scan Lifecycle States
Scan Not Started
Indicates that the scan has been created but no execution has been triggered.
Action:
- Click Run to start the scan
Running
A moving progress bar indicates that the scan is currently executing.
- Jobs are being submitted to security scanners
- Duration and start time are recorded
Submission Error
A red alert icon indicates that the scan was not successfully submitted to the underlying scanner.
This means:
- No job execution occurred
- The issue happened before scanning began
Action:
- Re-run the scan
- Verify scanner configuration
- Check integration and authentication settings
Failed
A red cross icon indicates that:
- The job was successfully submitted
- An error occurred during execution
Action:
- Expand the job list
- Review job duration and failure point
- Open error logs for detailed diagnostics
Partially Completed
A yellow icon indicates:
- At least one job succeeded
- At least one job failed
This is common in multi-scanner or multi-target scans.
Action:
- Expand the job list
- Identify failed jobs
- Review error logs for only the failed jobs
Completed
A green icon indicates:
- All jobs executed successfully
- No failures occurred
No action required.
Viewing Job Details
Click the arrow icon to expand the scan and view:
- Job status
- Execution duration
- Start and end time
Each job represents an independent security check.
Parallel Job Execution
Some scan types, such as CSPM, may create multiple jobs that run in parallel.
Example scenario:
- A scan launches 36 jobs simultaneously
- If one job fails and the rest succeed, the overall scan status becomes Partially Completed
Parallel execution reduces total scan time while maintaining granular visibility.
How Overall Scan Status Is Calculated
The overall scan status depends on the combination of job results:
- All jobs successful → Completed
- At least one job failed → Partially Completed
- All jobs failed → Failed
- Submission failure → Submission Error
- No execution → Scan Not Started
Field Reference
| Field | Description | Example |
|---|---|---|
| Scan Not Started | Scan created but not executed | Not started |
| Running | Scan currently executing | In progress |
| Submission Error | Scan not submitted to scanner | Error |
| Failed | Job execution failed | Failed |
| Partially Completed | Mixed success and failure across jobs | Partial |
| Completed | All jobs successful | Success |
| Arrow Icon | Expands job-level details | Expand jobs |
| Progress Bar | Indicates active scan execution | Running |