Investigating an Issue

Overview

Use this workflow when PI Nexus+ flags a problem:

1. Start from Dashboard or Issues. Use Dashboard to find high-impact issue groups, or use Issues when you already know the severity, category, or object name.
2. Open the object detail dialog. Click the issue row or object row.
3. Read the Issues tab first. Confirm the issue type, message, severity, days open, and whether it is already suppressed.
4. Check Usage or Datasources. Determine where the object is used and whether downstream objects are affected.
5. Open Dependency Graph. Trace upstream and downstream references. Look for the object that is broken earliest in the chain.
6. Check Change History. If the issue appeared recently, look for created, updated, renamed, moved, deleted, or excluded objects around the same time.
7. Fix the root cause outside PI Nexus+. Examples include restoring a PI Point, correcting an AF Attribute data reference, repairing an AF Analysis trigger/input/output, or correcting a PI Vision datasource.
8. Run the smallest meaningful scan. Use a scoped scan when the fix is limited to PI Points, Asset Framework, or PI Vision; use Full Inventory when the repair crosses domains.
9. Confirm the issue clears. Refresh the relevant page or return to the issue row after the scan completes.
10. Suppress only accepted exceptions. If the condition is intentionally allowed, suppress it with a clear reason and optional expiry.

For example, if a PI Vision display has a datasource error, do not stop at the display. Open the display detail, inspect the datasource references, follow the dependency graph to the AF Attribute or PI Point, and repair the source object that feeds the display.