← All patterns
Recurring Operational Drifthighstable4 occurrences
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
stable
Converted to evals
0 / 4
Recommended action
Escalate the incident workflow to enforce metric recovery at the status-update boundary and convert this cluster into a regression eval.
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.
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 | operational_signals: incident marked resolved, metric recovery failed, restart succeeded | Read trace |
| high | latent-false-success-drift | operational_signals: incident marked resolved, metric recovery failed, restart succeeded | Read trace |
| high | latent-false-success-drift | operational_signals: incident marked resolved, metric recovery failed, restart succeeded | Read trace |
| high | latent-false-success-drift | operational_signals: incident marked resolved, metric recovery failed, restart succeeded | Read trace |
Time window
2026-06-10T14:30:32.601Z/2026-06-10T14:30:32.601Z
Failure modes (1)
latent-false-success-drift
Shared evidence signals
operational ·4signals ·4incident ·4marked ·4resolved ·4metric ·4recovery ·4failed ·4restart ·4succeeded ·4verification ·4status ·4