# Fix it and confirm the fix worked

> Get a fix plan for an incident, hand it to your AI assistant, ship the fix, and let Relia confirm on real traffic that it worked.

Section: Use Relia every day · Page: https://tryrelia.com/docs/fix-and-verify · Last checked against the product: 2026-11-01
Video walkthrough: https://youtu.be/gtORFurIkow

When an incident needs you, Relia can write a fix plan from its evidence. After you ship the fix, Relia watches real traffic and tells you **"Your fix worked"** or **"Still happening after your fix"**.

## Before you start

- Fix plans come with **Growth** (30 a month) and **Pro** (50 a month). On Free, the incident page shows an upgrade card instead.
- Fix verification works on every plan.
- An open incident. See [How to read an incident](https://tryrelia.com/docs/incidents.md).

## Steps

1. Open the incident from **Home**.
2. Under **How to fix it**, click **Show how to fix**. Relia works out the fix from the evidence: failing requests, stack traces, database queries and server metrics.
3. Read the plan:
   - A one-line summary and the **Root cause**.
   - Up to 5 numbered steps. Each is labelled **Code**, **Database**, **Config**, **Server** or **Check**, says where (a file and line, a table, a setting) and what to change. **Copy** copies one step's change.
   - **Careful:** risks to keep in mind, and **How you'll know:** how to check it worked.
4. Make the change:
   - Click **Copy for your AI assistant** and paste the brief into Claude Code, Cursor or any assistant. It edits the code in your editor, with your approval.
   - Or let your assistant read the plan and the evidence from Relia itself. See [Fix bugs from your editor](https://tryrelia.com/docs/from-your-editor.md).
5. Deploy the fix as you normally do.
6. Click **I applied this fix** at the bottom of the plan, or **I fixed it** in the side column. If your app reports its version (Relia's SDKs do this from your commit or package version), Relia notices the deploy on its own and you don't need to click anything.

> **Important:** Relia never changes your code and has no access to your repository. Code lines are only sent to the AI writing the plan if you turn on **Source code in AI fix plans** (**Settings** → **Notifications** → **More options**).

Not happy with the plan? Click **Regenerate**.

> **Tip:** watch [Fix production bugs from your editor with Claude Code and Cursor](https://youtu.be/67fIYRYKZWk) (2 min) to hand the plan to your assistant.

## How Relia confirms the fix

After the fix lands, the side column shows **Checking your fix**. Relia then decides:

| Result | When |
|---|---|
| **Fix confirmed** | At least 20 requests reached the affected APIs over at least 15 minutes, and the problem never came back. For problems with no API (servers, pages), 30 quiet minutes. The incident is resolved and you get "Your fix worked". |
| **Still happening** | The problem showed up again after the fix. You get "Still happening after your fix" and can try again with **I fixed it again**. |
| **Not confirmed yet** | After 24 hours there still wasn't enough traffic to tell. |

You get each of these messages once, on the channels you chose in [notifications](https://tryrelia.com/docs/notifications.md).

## Rollbacks

If you connected a deploy platform (**Settings** → **Advanced** → **Integrations**) and a deploy caused the problem, Relia may propose a rollback on the incident page. Nothing runs until an owner or admin approves it; it then runs through your connected platform and Relia checks the result the same way.

> **Tip:** watch [A deploy broke checkout: find the cause and verify the fix](https://youtu.be/rRvqe6r_WRU) (2 min).

## Check the fix worked

- The incident's side column shows **Fix confirmed**, and the incident moves out of **For you** on Home.
- You receive "Your fix worked".

## If something's wrong

- **"This month's fix plans on the … plan (…) are used up"**: the plan's monthly allowance is spent. It renews on the 1st (UTC), or upgrade in **Team & plan**.
- **"Couldn't build a fix right now"**: try again in a minute.
- **The steps are vague about where to change code**: the plan only uses what Relia recorded. Upload [source maps](https://tryrelia.com/docs/source-maps.md) for browser errors, and make sure your server sends stack traces, so steps can name the file and line.
- **Stuck on Not confirmed yet**: the affected page or API gets little traffic. Check it yourself, then keep an eye on the incident.

## Next

- [Fix bugs from your editor](https://tryrelia.com/docs/from-your-editor.md)
- [Write a postmortem](https://tryrelia.com/docs/postmortems.md)
- [A deploy broke checkout](https://tryrelia.com/docs/deploy-broke-checkout.md)
- [Did my deploy break anything?](https://tryrelia.com/docs/did-my-deploy-break.md)

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