Recurring pattern
Latent False Success Drift in incident response
The same agent repeatedly shows service gaps, guardrail friction, or false-success behavior across completed traces.
Affected agent
Incident Agent
Occurrences
4
Trend
increasing
Converted to evals
1 / 4
Recommended action
Escalate to engineering leadership: DevOps agent has a systemic pattern of false incident resolution. Enforce mandatory metric-recovery verification at the workflow level. Promote this cluster to a regression eval.
Promote to a regression eval →Why this is a pattern, not a one-off
Increasing — this failure recurred across 4 traces and is accelerating. Treat it as a workflow/prompt/policy fix, not 4 separate tickets.
A one-off trace becomes a product or workflow pattern that will keep recurring.
Occurrences in this pattern (4)
Open as gap list →| Severity | Failure mode | Evidence | Trace |
|---|---|---|---|
| high | latent-false-success-drift | search_findings_history returned multiple prior False Success findings for agent-devops-01 on lens 'resolved-but-not-served'. | Read trace |
| high | latent-false-success-drift | search_findings_history returned multiple prior False Success findings for agent-devops-01 on lens 'resolved-but-not-served'. | Read trace |
| high | latent-false-success-drift | search_findings_history returned multiple prior False Success findings for agent-devops-01 on lens 'resolved-but-not-served'. | Read trace |
| high | latent-false-success-drift | search_findings_history returned multiple prior False Success findings for agent-devops-01 on lens 'resolved-but-not-served'. | Read trace |
Time window
2026-06-11T05:47:12.880Z/2026-06-11T05:47:15.783Z
Failure modes (1)
Shared evidence signals