# How to read an incident

> Read an incident from top to bottom: how bad it is, what happened, who it hit, why Relia thinks so, and the one thing to do next.

Section: Use Relia every day · Page: https://tryrelia.com/docs/incidents · Last checked against the product: 2026-11-01
Video walkthrough: https://youtu.be/5PDrogf7ZJU

When something goes wrong, Relia groups everything that belongs together (the failing API, the error behind it, the people who hit it, the deploy just before) into one **incident**. Open one from **Home** by clicking its row.

## How Relia sorts problems

| Bucket | Means | Alerts you? |
|---|---|---|
| **Needs you** | Broken for real people, or about to be. | Yes |
| **Worth watching** | Worth a look, not urgent. | Only if you chose **Everything** in [notifications](https://tryrelia.com/docs/notifications.md) |
| **Low priority** | Context. | No |

Relia decides this with fixed rules, not guesses: for example, most problems must be seen at least 3 times before they need you (a site that is down needs you at once), and a problem on a page or API you marked as must-never-break is raised sooner ([Teach Relia](https://tryrelia.com/docs/teach-relia.md)).

## The top

- The bucket (**Needs you**, **Worth watching** or **Low priority**), the severity (**critical**, **high**, **medium** or **low**), the kind (**Bug**, **Performance**, **Infrastructure**, **User experience**…) and the status (open, came back, resolved).
- The headline, such as "Placing an order fails after the 10:00 deploy".
- How many people it hit, sessions and failed requests, when it started and when it was last seen.
- If you [identify your users](https://tryrelia.com/docs/identify-users.md), how many signed-in customers it hit and their plans, with links to each person.
- **Mostly:** when the problem is concentrated in one browser, device, country or page.
- **Related problems and history**: similar problems on the same page or API, and whether this happened before.

## The story (Growth and Pro)

- **What happened**: the story in plain words. Every number comes from Relia's evidence.
- **How to fix it**: click **Show how to fix** for a fix plan. See [Fix it and confirm the fix worked](https://tryrelia.com/docs/fix-and-verify.md).
- **Why Relia thinks so**: Relia's confidence, and the links it found between parts of your stack.
  - **high**: linked end to end with a code or infrastructure cause.
  - **medium**: linked, but the exact cause isn't proven.
  - **low**: a pattern, not yet tied to a cause.
- **How it unfolded**: the steps in order. The first one is the likely origin, for example an error in the orders code right after a deploy.
- **Across your stack** (closed at first, click **Show**): one lane per layer (Users, Server, Database, Dependencies, Host, Changes and more), each finding with links. A session link opens the visitor's session at the moment it broke; a request link opens that request with its database queries and the error.

## The side column

- **Do this next**: the one thing to do.
- **I'm on it**: tells your team you're handling it and stops on-call paging. Viewers can't press it.
- **Fixed it?** → **I fixed it**: once your fix is out, Relia watches real traffic to confirm it.
- **Recent changes**: deploys, restarts and new servers around the time it started.
- **Is this right?**: tell Relia when it's wrong. See [Teach Relia when an alert is wrong](https://tryrelia.com/docs/feedback.md).

Some incidents also carry a question when Relia can't tell whether a behaviour is on purpose, with the answers **Yes, that's expected** and **No, that's a bug**.

> **Tip:** watch [Teach Relia when an alert is wrong (fewer false alarms)](https://youtu.be/QMYMDqJ98Y4) (2 min).

## On the Free plan

You still see the top: how bad it is, the headline, how many people it hit and when it started. The rest is replaced by **See why it happened and how to fix it**: "The explanation and the fix are part of the Growth plan." Relia still names how many findings it linked and across which layers.

## When an incident ends

An incident is resolved when the problem stops (after a quiet period), or when Relia confirms your fix worked. If it comes back, it reopens as "came back" and you get one message about it.

## Next

- [Fix it and confirm the fix worked](https://tryrelia.com/docs/fix-and-verify.md)
- [Teach Relia when an alert is wrong](https://tryrelia.com/docs/feedback.md)
- [Write a postmortem](https://tryrelia.com/docs/postmortems.md)
- [A deploy broke checkout](https://tryrelia.com/docs/deploy-broke-checkout.md)

---
All Relia docs for AI assistants: https://tryrelia.com/llms.txt (index) · https://tryrelia.com/llms-full.txt (everything in one file)
