Behavior of Sentry release health when a deployment yields no error events

Goal: Determine how Sentry’s release health algorithm labels a release as healthy, degraded, or crashy when a deployment fails but no error events are reported for that release.

Constraints: The health calculation uses a rolling window (default 24 hours) and requires a minimum traffic threshold before issuing a status. When no events are received, the algorithm treats the lack of data as zero errors, which may result in a healthy label. Exact thresholds and weighting factors are not exposed, and the health feature is available only on paid Sentry plans (Team, Business, Enterprise).

Specific questions:

• What minimum event or session count must be observed within the rolling window before Sentry can consider a release unhealthy?
• How does the 24‑hour rolling window interact with a deployment that produces zero events immediately after release?
• Is there a configuration or alternative metric that can be used to treat missing data as an unhealthy signal instead of healthy?