Documentation
Scan results
Follow running scans, understand failures, inspect discovered devices, retry scans and export results.
Overview
The Results tab of Scanning lists every scan execution: scheduled runs, Run now scans and retries. A sweep and the per-device scans it launches are grouped into one execution, so you see one row per run with its discovered devices underneath. Use this tab to follow scans as they run, find out why a scan failed, and retry it once the cause is fixed.
Screen tour
The Results tab has a toolbar above a table of executions:
- Search results…: filters by job ID, schedule, target or status.
- Status filters: All, Pending, Running, Completed and Failed, each with the number of executions in that state.
- Export CSV: downloads the executions currently shown, with their per-device jobs, as a CSV file.
- Status: the execution status and, for a failed scan, its error category. Hover over the category to see the error message.
- Progress: a progress bar. For a sweep it reads, for example, 12 of 40 inspected.
- View: opens the Scan result details.
- Retry (failed scans) or Re-run (completed scans): starts the scan again after you confirm.
The table also shows the Schedule, the Target and when the scan Started with its duration. Click the Status, Started or Progress header to sort. The newest executions come first. While any scan is pending or running, the tab refreshes every 2 seconds. When filters are active, Clear filters resets the search and status filter.
Execution statuses
| Status | Meaning | Next possible status |
|---|---|---|
| Pending | The scan is queued and waiting for a scanner. | Running, Failed |
| Running | The scan is in progress. A sweep shows Discovering while it looks for live hosts, then Collecting information while its per-device scans run. | Completed, Completed with issues, Failed |
| Completed | The scan finished and its findings are in the asset inventory. | Running (after Re-run) |
| Completed with issues | The sweep finished, but one or more of its per-device scans failed. | Running (after Re-run) |
| Failed | The scan could not finish. The error category explains why. | Running (after Retry) |
Error categories
A failed scan shows one of these categories, with a code and a suggested next step.
| Category | Code | Meaning and what to do |
|---|---|---|
| Auth failed | SCAN_AUTH_FAILED | The target rejected the login. Check the credential’s username, password or SSH key for this target. |
| Unreachable | SCAN_HOST_UNREACHABLE | The host could not be reached. Check the target address, the network route and firewall rules. |
| Timeout | SCAN_TIMEOUT | The target did not respond in time. Confirm it is online and reachable, then retry. |
| Agent timeout | SCAN_AGENT_TIMEOUT | The bridge host agent did not acknowledge the scan in time. Check that the agent is running and its heartbeat interval is 60 seconds or less. |
| No permission | SCAN_PERMISSION_DENIED | The login worked, but the account lacks the privileges the scan needs on the target. |
| No credential | SCAN_CREDENTIAL_MISSING | No credential is configured for this scan or target. Assign one and retry. |
| Invalid target | SCAN_INVALID_TARGET | The target and scan type do not fit together. Use Sweep for CIDR ranges, and one host for SSH, WMI or SNMP. |
| Protocol error | SCAN_PROTOCOL_ERROR | The target answered with an unexpected protocol response. Check that the right service listens on the port. |
| Internal error | SCAN_INTERNAL | Something else went wrong. Read the error message and the scan log for details. |
| Stalled | SCAN_ORPHANED | The scan ran longer than its maximum runtime or its worker stopped without reporting, so it was marked failed. Retry the scan. |
Inspect the devices of a sweep
When a sweep discovers devices, the Schedule cell becomes a toggle. Click it to show the devices underneath the row.
- The summary line counts the devices Discovered, Inspected, Authenticated and those with Issues.
- Filter the list with All, Successful or Issues.
- Each device shows its state: Authenticated when the follow-up scan collected its inventory, the error category (for example Auth failed) when it failed, Collecting while it runs, or Waiting while it is queued.
- Click View to open that device’s scan result, or Retry to rescan just that device.
View a scan result
Click View on a row to open the Scan result modal. It refreshes itself while the scan is running. It contains:
- Status and attempt: the job status and Attempt N, which counts retries of the same job.
- Scan failed: for a failed scan, the error category, the error code, the suggested next step and the full error message.
- Job details: Job ID, Schedule, Target, Started, Completed, Duration, and Assets found (for a sweep, Machines discovered).
- Scan log: every event the scan recorded, with its phase, message and time, for example Applied scan profile “Web ports sweep”: … or Scan complete — 12 assets discovered. When the log needs reloading, a Retry button appears under Scan log.
For a sweep, the Authenticated follow-up section summarizes the per-device scans: how many machines were discovered, how many were inventoried, how many need attention and how many are still in progress. Click Show devices to see a table with each Machine, its Access result (Inventory collected, In progress, Needs credential attention or Scan failed), the Reason and the Next step. If no device scans were launched, the section reads No authenticated device scans were launched. Assign a credential to the schedule, or a default credential to the assets, to enable them.
Click Close to close the modal.
Retry or re-run a scan
- Click Retry on a failed execution, or Re-run on a completed one.
- Read the dialog. For a sweep, Retry restarts the whole scan, including devices that already succeeded. Results already collected are kept.
- Click Retry scan or Re-run scan.
The new attempt appears at the top of the list. To retry only one failed device of a sweep, expand the sweep and click Retry on that device.
Export results to CSV
Click Export CSV. The file is named scan-results-<timestamp>.csv and contains the executions that match the current search and status filter, including each sweep’s per-device jobs. Columns:
id, schedule, target, vendor, status, startedAt, completedAt, progress%, found, errors, errorCategory, errorMessage
Values that start with =, +, - or @ are prefixed with ' so that spreadsheet programs do not run them as formulas.
Keyboard shortcuts
| Key | Action |
|---|---|
| ← / → (or ↑ / ↓) | With focus on the status filters, select the previous or next filter. |
| Home / End | With focus on the status filters, select the first or last filter. |