Runbook: Sentry Critical Error
Trigger
Use this runbook when Sentry reports a critical or recurring production application error.
Immediate Actions
| Step | Action | Owner | Evidence | Status |
|---|---|---|---|---|
| 1 | Open the Sentry issue and confirm environment | Backend | Sentry screenshot without secrets | TBD |
| 2 | Identify affected release, endpoint, user flow, and frequency | Backend / QA | Issue metadata | TBD |
| 3 | Check if the error affects payments, credentials, RBAC, or tenant isolation | Incident Commander | Impact note | TBD |
| 4 | Review recent deployment or config changes | Release Owner | Deployment record | TBD |
| 5 | Create defect or incident based on impact | QA / Incident Commander | Defect or incident link | TBD |
| 6 | Verify fix and monitor for recurrence | Backend / QA | Sentry resolution evidence | TBD |
Severity Guidance
| Condition | Severity |
|---|---|
| Payment, wallet, data exposure, or tenant isolation risk | SEV-1 |
| Login or core API failure | SEV-1 / SEV-2 |
| Repeated production exception with user impact | SEV-2 |
| Isolated non-critical exception | SEV-3 / SEV-4 |
Closure Criteria
- Root cause is identified.
- Fix or mitigation is deployed.
- Sentry issue is resolved or no longer recurring.
- Regression test is added where appropriate.