Skip to main content

​
Overview

Incidents are the Trust operator inbox. When a gated quality check fails after a sync or run, an incident lands here so you can triage and clear the gate without relying only on raw Job logs. To open the inbox:
  1. Select Trust → Incidents in the application sidebar.
The page title is Trust incidents.

​
Page controls

Header actions: Filters below the header: Optional URL scope:
  • ?job=<job_id> — show incidents for one Job
  • ?asset=<asset_id> — show incidents for one asset
Use Clear on the scope banner to return to the full inbox.
The “shown” count reflects the current filters (status, severity, search, and URL scope). It is not a separate global KPI disconnected from the list.

​
Incident statuses

​
Triage procedure

  1. Open Trust → Incidents.
  2. Filter to Open (default).
  3. Optionally narrow by severity or search.
  4. On an incident row:
    • Set Assign steward (org member), or clear assignee
    • Click Investigate (from open) to mark investigating
    • Click Cleanse when a Job is linked (opens Cleanse as MOVE)
    • Click Resolve when the failure is cleared
    • Use overflow (More) for Open in catalog, Quality rules, Open job, or Create Match project
  5. Re-run detect or the related Job as needed after remediation.

​
Cleanse as MOVE

Cleanse is available when the incident has a linked Job and is not resolved.
  1. Click Cleanse.
  2. In Cleanse as MOVE, set column / operation / value and optional standardize options (trim, lower, email, phone).
  3. Confirm. Zwiron creates a cleanse Job and attempts to start it.
For duplicate-entity problems, prefer Create Match project (overflow) instead of cleanse filters.

​
Create Match project from an incident

When the incident has a linked Job and is not resolved, overflow → Create Match project creates a Match project from the incident context and navigates to that project. See Match projects.
Last modified on October 10, 2026