---
name: sentry-release-health
description: Check a release in Sentry after deploy for new issues, regressions, error spikes and slower transactions, and compare it with the previous release to decide whether it is safe or needs a rollback. Use when the user asks how a release or deploy is doing, whether it broke anything, or whether to roll back.
---

# Release health check

Read-only.

## Steps

1. Find the release with `find_releases`, defaulting to the latest in production, and the release before it.
2. New problems: `find_issues` with `firstSeen` inside the release window and `release:<version>`. Separate brand-new issues from regressions, which are resolved issues that came back.
3. Volume: `find_errors` for the error count and users affected in this release against the previous one over the same length of time after deploy.
4. Performance: `find_transactions` for the slowest or most-changed endpoints and pages, with p75 or p95 duration before and after.
5. Open the top two or three new issues with `get_issue_details` to judge their severity: a crash in checkout outweighs a noisy console warning.

## Verdict

- Healthy, watch or roll back, with the one or two facts that decide it.
- New issues and regressions, by users affected.
- Performance changes over about 20%.
- Anything you could not measure because there was too little traffic yet.