PI Nexus+ / Reference
Scan Runs Reference
This reference lists the kinds of scan work, what starts them, their scopes and their outcomes, as the Scanning page and the scan history show them.
Overview
This reference lists the kinds of scan work, what starts them, their scopes and their outcomes, as the Scanning page and the scan history show them.
Kinds of work
| Shown as | What it does | Advances |
|---|---|---|
| Inventory scan | Full discovery of a target's inventory | Inventory freshness (on success) |
| Full verification | An automatic full inventory scan run as a cross-check at the verification cadence | Inventory freshness and the verification date |
| Inventory update | Reloads only the objects a change feed reported, or the object a user chose Update inventory on | Last inventory update only |
| Health refresh | Re-reads current values and health rules for known inventory | Health freshness (see Health refresh credit) |
| Health check | Check health on one PI Point, AF Attribute, AF Analysis, PI Interface or PI Adapter Collector; runs beside other work and is shown only on that object | Nothing on the target |
| Missing inventory purge (badge Maintenance) | Deletes all missing inventory; queued from Admin > Inventory Maintenance | Nothing |
Triggers
| Trigger shown | Started by | Waits for the heavy-work window | Sends a completion email |
|---|---|---|---|
| Manual | A person, from the Scanning page or an Admin page | No | Yes, under Manual scan completion |
| Run now | A person promoting queued automatic work | No | Yes |
| Automatic | Automatic monitoring | Full scans only | No; failures after the last retry send Automatic monitoring failures |
| Configuration | A configuration change, such as the PI Point rule reconciliation | Yes | No |
| Schedule | A recurring schedule from before 1.6.0 that has not been retired | No | Yes |
Scopes
| Scope | Reconcile inventory | Refresh health |
|---|---|---|
| Full inventory / All operational health | All enabled PI Data Archives, AF databases and PI Vision instances, as one run | PI Points and Asset Framework, as one run |
| PI Points | Chosen PI Data Archives, optionally only some PI Point rules | Chosen PI Data Archives (always all rules) |
| Asset Framework | One run per chosen AF database | One run per chosen AF database |
| PI Interfaces | PI Module Database of chosen PI Data Archives with Interface Tracking on | Not offered |
| PI Vision | Chosen PI Vision instances | Not offered |
An empty selection is refused, as are an unknown, disabled or mismatched AF database. An AF Server with no enabled database scans nothing. AF databases that were not chosen are never marked missing.
A run narrowed to some PI Point rules does not advance the PI Data Archive's inventory or health freshness, does not count as a baseline, does not reset failure counters and does not retire a queued full scan.
Outcomes
| Outcome | Meaning | Completion email box |
|---|---|---|
| Queued | Waiting to start | |
| Running | In progress | |
| Succeeded | Finished without errors | Succeeded |
| Completed with errors | Finished, but some objects or modules failed; the run lists them | Failed |
| Failed | Did not finish | Failed |
| Canceled | Stopped by a person, or ended by Recover | Canceled |
| Skipped | Not run, because another scan held the scan lock when it was due to start | Skipped |
| Dispatch failed | Shown in the Health column when automatic monitoring could not start a refresh at all |
Failed, canceled, skipped and completed-with-errors inventory work stays due and is tried again; it never advances inventory freshness.
Health refresh credit
A health refresh that ends Completed with errors still advances health freshness when it refreshed at least 90 % of the objects it set out to refresh. The run keeps its real outcome and failure list; its message states the coverage. A run that refreshed nothing is never credited.
Failure classes
| Class | Retried automatically |
|---|---|
| Transient Infrastructure | Yes |
| Unknown Infrastructure | Yes |
| Configuration | No |
| Validation | No |
| Authorization | No |
| Unsupported Scope | No |
Needs attention
The Needs attention tab lists, per target:
| Text | Meaning |
|---|---|
| Health refresh failed N times in a row | Health refreshes keep failing |
| Health refresh is due | Health is older than its cadence |
| Inventory reconciliation failed N times in a row | Inventory scans keep failing |
| Inventory reconciliation is due | Inventory is older than its cadence |
| Health / Inventory paused for attention | Automatic work stopped retrying and waits for a person (Retry) |
Stuck scans
| Item | Value |
|---|---|
| Recover offered for a running scan | No progress reported for 30 minutes |
| Recover offered for a queued run | Not started after 10 minutes |
| Role | Admin |
| Refused when | A live scanner process still owns the scan; stop the PI Nexus+ Scanner service first |
Delete a scan run
Deleting a single run is a support action, not a substitute for retention. It needs the Admin role.
- In the Scanning page's History tab, or in a target's history, open the row menu of a finished run and choose Permanently delete.
- Read the list of records that go with the run. PI Nexus+ refuses when the run is still needed: active work, current inventory, retained change history or pending emails.
- Confirm. Deleting a target's latest health result returns the target to unknown health and makes a new health refresh due; the button then reads Delete and refresh state.
Each deletion is written to the security audit.
Updated objects
Open an Inventory update run to see Updated objects: each AF element, analysis, template, PI Point or PI Vision display, what happened to it (added, updated, removed, template changed) and when the source reported it. A queued update shows the same list as Waiting to update N objects. Long lists are cut and the dialog says how many more there are. An update requested on an AF attribute or analysis reloads its whole element, so the run names the element.
