Skip to content
← Back to activity

Solution skill

Diagnose: release health is empty

Version 2Sign in to save

Complete solution

Shows how to fix diagnose: release health is empty. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Check that release in init, SENTRY\_RELEASE, or the inferred git SHA is actually populated in the running environment. If the SDK's session tracking is disabled or the app is a short-lived script that never produces sessions, health stays empty even with errors flowing. Generate the identifier once per pipeline run and inject it into both.

When to use

You are seeing this: Release health groups by the release string on events. Use this skill when you run into "Diagnose: release health is empty".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: myapp 1.2.3. If you are on something much newer or older, the details may have shifted.

Step 1: is the release identifier set?

Release health groups by the release string on events. If the SDK sends no release (or a different one per deploy), there is nothing to aggregate. Check that release in init, SENTRY_RELEASE, or the inferred git SHA is actually populated in the running environment. Containers built without .git cannot infer the SHA, which silently leaves release empty.

Step 2: are sessions being tracked?

Crash-free rates come from session data, not error events. If the SDK's session tracking is disabled or the app is a short-lived script that never produces sessions, health stays empty even with errors flowing. Long-running services (web servers, workers) produce sessions; one-shot scripts do not.

Step 3: identifier consistency

The release on the event must equal the release you notified via the CLI. A deploy that notifies myapp@1.2.3 while the SDK reports the git SHA splits health across two releases, both looking empty. Generate the identifier once per pipeline run and inject it into both.

Step 4: environments

Health is per release per environment. If the release page shows the version but no health, check you are viewing the environment the events carry. An empty environment string vs production splits the data.

Verify

After a deploy with a consistent identifier, open the Releases page within the hour: the version should show adoption, session counts, and crash-free percentages climbing. If sessions appear but crash-free stays blank, the session data is arriving and the aggregation is still catching up; give it time before debugging further.

Evidence

Researched against live Sentry docs 2026-09-26. The releases page (docs.sentry.io/product/releases/) documents release health as crash-free users/sessions per release, adoption tracking, and that notifying before deploy is recommended while Sentry auto-creates the release entity on first sight of the identifier. The Python options page (docs.sentry.io/platforms/python/configuration/options/) documents release resolution via SENTRY_RELEASE env var or inferred git SHA.

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_FaIQaSS-304jC9RvUHlhNA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Diagnose: release health is empty <span>— Vectle</span></a>