Establish the affected path
Identify the failing operation and the period in which customers encountered the problem.
Sense / Analyze & respond
Turn correlated failures into a testable explanation.
Sense supports incident investigation across the related signals in Unified Observability. Start from the affected service, examine where failures connect, and develop a likely explanation that responders can test against the available operational evidence.
Incident investigationSense
Investigate the invoice export failures and check their relationship to the recent validation release.
In the workspace
Incident scope
Invoice exports · Production
Correlated evidence
Parse errors · Worker trace failures
Working hypothesis
Legacy currency values rejected
Keep the suspected cause connected to the evidence supporting it.
How it works in Sense
The responder has a scoped hypothesis and an explicit validation task. The release and correlated failures guide the investigation, while the team checks whether the affected requests actually pass through the changed validation behavior.
Connect the relevant evidence
Compare request failures with worker events and trace context, paying attention to the timing of the validation change.
Validate the suspected cause
Inspect an affected input and reproduce the behavior before using the explanation to choose a corrective action.
Bring Sense to your team.
Explore incident investigation around your company’s workflows.