← All patterns
False Resolutionhighstable4 occurrences
Recurring pattern
False Success in incident response
The agent marked the work resolved while verification evidence still showed the underlying problem was active.
Affected agent
Incident Agent
Occurrences
4
Trend
stable
Converted to evals
0 / 4
Recommended action
Require recovery verification to pass before incident status can be set to resolved. Treat restart success as an intermediate action rather than the customer outcome.
Promote to a regression eval →Why this is a pattern, not a one-off
Stable — recurring (4 traces) but not accelerating. Still worth a systemic fix.
Internal status says done, but customers or operators still experience the failure.
Occurrences in this pattern (4)
Open as gap list →| Severity | Failure mode | Evidence | Trace |
|---|---|---|---|
| critical | False Success | agent_status: resolved | Read trace |
| critical | False Success | agent_status: resolved | Read trace |
| critical | False Success | agent_status: resolved | Read trace |
| critical | False Success | agent_status: resolved | Read trace |
Time window
2026-06-10T14:30:32.601Z/2026-06-10T14:30:32.601Z
Failure modes (1)
False Success
Shared evidence signals
agent ·4status ·4resolved ·4restart ·4service ·4restarted ·4pods ·4healthy ·4metric ·4recovery ·4verification ·4failed ·4