Skip to main content
A finding explains why an operation did not meet its expected evidence timeline. It connects the expected stage, the observed events, the deadline, and the resulting status, and it leaves the underlying evidence untouched.

​
Categories

The category is the deterministic reason the finding was raised, and each one points at a different kind of problem.

​
Statuses

The public API reports three statuses, and the dashboard’s acknowledged and investigating steps stay internal to investigation.
  • open means the finding still needs attention.
  • resolved means the expected evidence arrived on time.
  • resolved_late means the evidence arrived after the deadline, and the breach stays in the history.

​
Investigate a finding

Investigation lives in the dashboard, which means your event sender implements none of this workflow. The evidence reads in a fixed order:
1

Confirm the reference

The issue matches one operation reference and one affected target.
2

Read the timeline

Event types, occurred times, received times, and expected stages sit side by side.
3

Choose the next action

The outcome is a corrected source workflow, a pending event worth waiting for, or an investigation recorded through the dashboard or a supported API operation.
The public API exposes issue reads, assignment, and append-only notes for integrations that need automation. Issue operations covers those routes.
Finding messages and identifiers can contain financial data. Redact them in logs and support tickets.