# Incident Postmortem Sample

## Input snapshot

At 09:10 Sentry alerted on generation insert failures. By 09:18 support reported user-facing errors. At 09:26 the team traced the issue to a schema mismatch on generations insert. A rollback landed at 09:48. Writes recovered by 10:05 and monitoring stabilized by 10:25.

## Output snapshot

### Root Cause

A schema mismatch caused writes to fail during generation persistence, which broke saved-output creation for affected requests.

### Prevention Actions

- Add migration verification to release readiness
- Expand persistence-path tests
- Add alerting for generation insert failures

### Why this sample matters

This example shows how an incident timeline becomes a clearer learning document with root cause, impact, and prevention follow-through.
