Billing Members receive infinite loading spinner when accessing pages they do not have permissions for

### Environment

SaaS ([https://sentry.io/]())

### Steps to Reproduce

1. Log in to an org as a Billing member.
2. Be redirected to the Issue stream which a Billing member has no access
3. See infinite Load

I tried multiple times, and one time I did receive the banner "You do not have permission to access this page". I believe this used to pop up every time in the previous UI.

Should the UI redirect to the Subscription directly for billing members instead of to a page the user has no access?

The video below is cut off at the end, but the Subscription Page loads as expected for Billing Members

[https://github.com/user-attachments/assets/57c3d90e-8ffe-45b4-bd6d-fd03e50906e5]()

### Expected Result

Either a consistent banner explaining why the user sees no data, or a redirect to a page the user has access to.

### Actual Result

Infinite load, which is confusing.

### Product Area

Settings - Members

### Link

*No response*

### DSN

*No response*

### Version

*No response*

We want to define a set of [lightweight metrics]() that SDKs can automatically collect for e.g. framework, language or platform, focusing only on signals that **do NOT overlap with Tracing**. Ideally these metrics should give a quick sense of app or runtime health, … while deeper investigation will still rely on traces or profiles.

Examples**:**

* Node.js runtime metrics (e.g., event loop delay, heap usage)
* Prisma-related metrics in Next.js
* Mobile CPU / memory usage to help surface potential ANRs or app hangs

---

**Candidate Metrics (add more below)**

* …

*(please also add ideas, questions or examples in comments)*

Start by reproducing the infinite loading state with a Billing member entering the Issue stream, then compare it with the expected permission banner and the accessible Subscription page. Determine whether completion should be a consistent permission message or a redirect, and verify the selected behavior across the reported access path.

Written by the indexing model from the issue text.