.png)
Blog
Insights & updates from our experts
Reading Scan Results and Discovery Failures
See what a scan found, what happens to it next, and why some devices failed.
Results are uploaded as one file when the scan finishes, so a running scan shows no devices yet. Open the scan to see its progress, its timing (hub queue, run time) and its result summary.
What happens to the results
Each discovered device is processed into CI Reconciliation. The scan page reports how many devices were found and how many are new or already known, and links to Review CI Reconciliations. Each device ends in one of these outcomes:
| Outcome | Meaning |
|---|---|
| Staged for reconciliation | Queued for you to review before the CMDB changes |
| Held for review | Needs a decision from a person |
| Unchanged | The device matched its configuration item, so no review is needed |
| Rejected during processing | The result could not be used. The scan page gives the reason. |
If CI Reconciliation is not enabled in account settings, results are held and processed as soon as it is. If two devices report the same source ID, only one is added for review. Give each device its own source ID and scan again. See Getting Started with Reconciliation for the review process, and Reconciling Discovered Devices and AI Product Suggestions for how discovered products and operating systems are chosen.
Discovery Failures
Every address in the scan gets a result, including those that failed. The Discovery Failures section of the scan lists each failed address with a port, a status, a reason and a short detail. The same rows appear on the configuration item the address resolved to. Failures are kept for 30 days after the scan was created, and a later success for the same address replaces the failure.
| Status | In plain words | Usually fixed by |
|---|---|---|
succeeded | The device was read | Nothing |
partial | The device answered, but a time or size limit cut the read short | Service Desk with the infrastructure team |
unreachable | The hub could not reach the device or its listener | Network team |
timeout | The device did not answer in time | Network or device team |
auth_failed | The device answered and refused the credential or account | Device or account team |
malformed | The device answered in a way the hub could not complete | Device team |
credentials_unavailable | The hub held back a credential after repeated refusals, or could not fetch it | Credential owner |
failed | Cause unknown, a hub fault, or an unsupported platform | Xurrent Support |
Group the failed rows by reason. One reason across many devices points to a shared cause such as a credential, a firewall or a hub setting. Different reasons on single devices point to problems with those devices. See Troubleshooting Native Discovery for what to check.
Open Modal