← All patterns
False Resolutioncriticalstable12 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

12

Trend

stable

Converted to evals

0 / 12

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 (12 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 (12)

Open as gap list →
SeverityFailure modeEvidenceTrace
criticalFalse Successagent_status: resolvedRead trace
criticalFalse Successagent_status: resolvedRead trace
criticalFalse Successagent_status: resolvedRead trace
criticalFalse Successagent_status: resolvedRead trace
criticalFalse Successagent_status: resolvedRead trace
criticalFalse Successagent_status: resolvedRead trace
criticalFalse Successagent_status: resolvedRead trace
criticalFalse Successagent_status: resolvedRead trace
criticalFalse Successagent_status: resolvedRead trace
criticalFalse Successagent_status: resolvedRead trace
criticalFalse Successagent_status: resolvedRead trace
criticalFalse Successagent_status: resolvedRead trace

Time window

2026-06-10T14:30:32.601Z/2026-06-11T05:47:29.662Z

Failure modes (1)

False Success

Shared evidence signals

agent ·12status ·12resolved ·12restart ·12service ·12restarted ·12pods ·12healthy ·12metric ·12recovery ·12verification ·12failed ·12