Docs Find and fix real problems
Did my deploy break anything?
After a release, ask Relia whether anything got worse, compare before and after on a chart with the deploy marked, or run the same check from your editor.
You just shipped. Nothing is on fire, but did anything get worse: new errors, a slower API, a slower page? This page shows three ways to check, and what Relia does on its own when a deploy does break something.
The example is Relia's demo shop: it ships api 1.12 at 15:00. Nothing breaks, but the product list gets slower.
Before you start
Relia has to know about your deploys. It sees one when a service starts reporting a new version. The Node.js and Python SDKs read the version from RELIA_RELEASE, SERVICE_VERSION or OTEL_SERVICE_VERSION, else from your host's commit variable (for example GITHUB_SHA, VERCEL_GIT_COMMIT_SHA, RENDER_GIT_COMMIT), else from .git or your package.json (Python: pyproject.toml) version. If yours never changes, set RELIA_RELEASE in your deploy, or report each deploy yourself (see Report changes).
What you'll see
There is no separate release screen. A deploy shows up wherever it matters:
- When it breaks something: Relia opens an incident on its own. If the problem started right after the deploy, Recent changes on the incident lists it, and Do this next names the release: This started right after api 1.12 was deployed: check that release or roll back to 1.11.1. See A deploy broke something important.
- On dashboards you make: on time charts, a deploy is a dashed line. Under a chart with one line, a sentence compares before and after, for example response time is 71% higher since that deploy. It only appears when the change is at least 20% and bigger than the chart's usual ups and downs.
Find the cause
Ask Relia
Open Ask Relia in the menu.
Type your question and send it:
Did the last deploy cause any problems?Read the answer. It starts with a one-line verdict (for example nothing broke, but the product list got slower), then short points: new incidents, new errors, slower APIs. Each claim links to its evidence.
Ask a follow-up to see it on a chart, for example show me the response time of GET /api/products over the last 6 hours. To see the deploy marked on the chart, ask Relia to make a dashboard with it (for example make me a dashboard for the product list): dashboard charts mark deploys.
Ask Relia is on every plan. Free includes 30 questions a month.
Tip: watch Ask your production data questions in plain English (2 min).
From your editor
If your AI assistant is connected to Relia, run Relia's deploy-check prompt (in Claude Code: /mcp__relia__deploy-check), or just ask did my last deploy break anything?. It reads the recent changes, finds the latest deploy, and compares before and after: incidents, errors, slow requests and database queries. It tells you in plain words whether the deploy is fine, and if not, what broke and where in the code.
Tip: watch Fix production bugs from your editor with Claude Code and Cursor (2 min).
On a dashboard
Your service's dashboard (Dashboards, then the service) lists the versions it ran, with restarts. Charts in a dashboard you make (Dashboards, then New dashboard, or "make me a dashboard" in Ask Relia) mark each deploy with a dashed line. See Dashboards.
Fix it
- Something broke: roll back to the previous version, or fix forward. On Growth and Pro, Show how to fix on the incident writes the steps.
- Something got slower: open a slow request and see what it waits on. See Why is my API slow?
Check the fix worked
Ship the fix (for example api 1.12.1). Relia picks up the new version by itself and starts checking any open incident on real traffic: you get Your fix worked or Still happening after your fix. On a dashboard chart the new deploy is a second dashed line, and the sentence under it compares before and after the newest deploy.
Next
Last checked against the product: 1 Nov 2026