In Tenable.io, depending on its state, scans can have following status values.
|Vulnerability Management Scans|
Either the latest run of the scan is incomplete because Tenable.io or the scanner encountered problems during the run, or the scan remained queued without running for four or more hours. For more information about the problems encountered during the run, view the scan warnings.
At user request, Tenable.io successfully stopped the latest run of the scan.
The latest run of the scan is complete.
The scan is either empty (the scan is new or has yet to run) or pending (Tenable.io is processing a request to run the scan).
A user imported the scan. You cannot run imported scans. Scan history is unavailable for imported scans.
A user paused the scan, and Tenable.io is processing the action.
|Paused||At user request, Tenable.io successfully paused active tasks related to the scan. The paused tasks continue to fill the task capacity of the scanner that the tasks were assigned to. Tenable.io does not dispatch new tasks from a paused scan job. If the scan remains in a paused state for more than 14 days, the scan times out. Tenable.io then aborts the related tasks on the scanner and categorizes the scan as aborted.|
|Processing||Tenable.io is processing tasks for the scan. For example, Tenable.io may be importing scan results from the scanner that performed the latest run of the scan.|
|Resuming||Tenable.io is in the process of restarting tasks after the user resumed the scan. Tenable.io instructs the scanner to start the tasks from the point at which the scan was paused. If Tenable.io or the scanner encounters problems when resuming the scan, the scan fails, and Tenable.io updates the scan status to aborted.|
The scan is currently running.
|Stopping||A user stopped the scan, and Tenable.io is processing the action.|
|Web Application Scans|
The scanner did not complete the scan's latest scan job. Tenable.io Web Application Scanning may abort a scan job because the job was queued without running for more than four hours, or because Tenable.io Web Application Scanning, or the scanner, encountered other problems and aborted the scan.
For more information about why Tenable.io Web Application Scanning aborted a scan, view the scan notes.
At the user's request, Tenable.io Web Application Scanning successfully stopped the latest scan job.
|Completed||The scanner completed the scan's latest scan job.|
|Never Run||The scan is either empty (the scan is new or has yet to run) or pending (Tenable.io Web Application Scanning is processing a request to run the scan).|
Tenable.io Web Application Scanning has the scan queued to launch.
Note: Tenable.io Web Application Scanning aborts scans that remain in pending status for more than four hours. If Tenable.io Web Application Scanning aborts your scan, modify your scan schedules to reduce the number of overlapping scans. If you still have issues, contact Tenable Support.
|Processing||The scan has completed but the results are still being processed. The scanner is processing vulnerability findings, attachments, notes, and other metadata.|
The scanner is currently running the scan.
|Stopping||The scanner acknowledged the stop request and is in the process of stopping.|