V2 UI Reference: Problem Devices Tab

The Problem Devices tab is where every candidate that did not sail through the V2 pipeline lands for review. It groups problems by category and lists each affected candidate so you can fix the upstream data, the rConfig configuration, or the reconciliation policy and re-run.

This tab is identical across all V2 drivers: the categories come from the pipeline, not the driver.

When to Use This Tab

Check Problem Devices after any Preview Sync or Full Sync to see what the pipeline could not resolve automatically. Use it whenever the Open Problems count on Run Insights is greater than zero, or whenever a Full Sync creates or updates fewer devices than you expected.

A completed run can still leave problems

A “completed” run can still leave Problem Devices behind. The Run Insights Open Problems card and this tab are the authoritative measure of whether your sync did everything you wanted.

Prerequisites

• A V2 integration instance that has completed at least one Preview Sync or Full Sync run.
• setting.view permission to view the tab.

What “Problem” Means in V2

Anything that keeps a candidate from reaching a clean create or update decision produces an open conflict record, which shows up here. The pipeline creates these at two points:

Stage	What triggers it
canonicalize	The candidate failed validation: most commonly a missing required Device Profile tag, or another canonical field the schema requires.
decide	Reconciliation returned a medium or ambiguous match tier, so the decision requires manual review instead of an automatic update or create.

A candidate has at most one open conflict at a time. Fixing the upstream record (or resolving the conflict manually) and re-running either clears it or, if a different problem surfaces, moves it to a different group.

Reading the Tab

The layout is group summary cards on top, a detail table underneath.

Group Summary Cards

Each group gets its own card, colour-rotated through a six-tone palette so adjacent groups are easy to tell apart. Only groups with at least one open conflict for the latest run are shown.

Group key	Card label	What it means
missing_required_tag	Missing required tag	The candidate was rejected in canonicalize because it lacks the Device Profile tag the schema requires (for example, Zabbix’s rconfig::device_profile tag, which is required by default).
mapping_failure	Mapping failure	Validation failed with a mapping-related reason code: the driver could not resolve a required field from the upstream payload.
validation_rejected	Validation rejected	The candidate failed canonical validation for a reason other than a missing Device Profile tag or a mapping failure.
reconciliation_conflict	Reconciliation conflict / manual review	Reconciliation returned a medium match (one plausible existing device) or an ambiguous match (more than one), so decide could not resolve it automatically.

Every open conflict currently shows as medium severity

Every conflict raised by the pipeline today is written with severity: medium, which the tab renders as an amber badge. The UI also supports critical/high/error (red) and info/low (sky) severities for future use: if you see a different colour, treat it the same way: red blocks Apply, amber defers it for review.

Detail Table

Column	What it shows
Reason	The group key for this row: same value as the summary card heading. Acts as the primary triage filter.
Host	Hostname from the candidate’s canonical payload (may be empty for rejected candidates that never resolved a hostname).
External ID	Upstream identifier: use this to cross-reference back to the upstream system.
Severity	Coloured badge, red for critical/high/error, amber for warning/medium, sky for info/low. Every row is currently amber (medium).

Pagination & Refresh

• Refresh icon (top right): re-fetches the latest run’s open problems. Use it after re-running with policy or upstream changes to see what is left.
• Previous / Next: page through long problem lists. The problem set for the latest run is paginated server-side.

Triage Workflow

For each problem row:

1. Identify the row by External ID and Host. Open the upstream system in another tab.
2. Read the Reason to know what to fix:
   • missing_required_tag: add the required Device Profile tag or custom field on the upstream record (see the driver’s Device Profile section), then re-run.
   • mapping_failure or validation_rejected: open the row and check validation_errors in the conflict details for the specific field that failed, then fix it upstream.
   • reconciliation_conflict: open the candidate, review which existing rConfig device it matched (or the multiple devices it matched, for an ambiguous case), and pick the correct target or merge/retire the duplicate.
3. Re-run a Preview Sync to confirm the row clears (or moves to a different group).
4. Run Full Sync once the open problem count for the categories you care about is zero.

What Gets Cleared by What

Problem group	Cleared by
missing_required_tag	Adding the required Device Profile tag or custom field upstream, then re-running.
mapping_failure	Fixing the upstream field the driver could not map, then re-running.
validation_rejected	Fixing whatever canonical field failed validation, then re-running.
reconciliation_conflict	Manual resolution: pick or confirm the target device. No automatic clear.

Common Gotchas

Common gotchas

• A candidate with an open conflict is always decided as skip: it will not create or update a device until the conflict clears, even in Apply mode.
• Every conflict currently renders with the same amber “medium” severity badge, so don’t rely on colour alone to judge urgency: read the Reason column instead.
• Refreshing the tab only re-fetches the latest run’s problems. It does not re-run the pipeline: use Preview Sync or Full Sync for that.
• missing_required_tag only fires for drivers whose schema marks the Device Profile as required (Zabbix, by default). Drivers where the profile is advisory (Nautobot, NetBox) will not reject a candidate just for missing it.

Related Documentation

• Run Insights Tab: the high-level counters that summarise the totals shown here.
• Logs Tab: per-stage error payloads behind each problem row.
• Device Sync V2 Overview: links to every driver’s Device Profile and setup conventions.