fix(event): Prevent immediate retry of rate-limited org in event view fallback

[sentry]

This PR fixes an issue where the sentry event view command could trigger a "Consecutive HTTP" performance issue (CLI-2Y1).

Root Cause:
When fetchEventWithContext falls back to tryEventFallbacks and resolveEventInOrg hits a 429 (Too Many Requests) rate limit, the error was caught as a generic transient failure. This left sameOrgSearched as false, causing the subsequent findEventAcrossOrgs call to immediately retry the exact same rate-limited endpoint for the same organization. This back-to-back identical request against a rate-limited API endpoint caused the performance issue.

Solution:

1. Introduce an orgRateLimited flag in tryEventFallbacks.
2. When resolveEventInOrg catches an ApiError with status 429, set orgRateLimited = true.
3. Modify the excludeOrgs logic for findEventAcrossOrgs to exclude the organization if sameOrgSearched is true (meaning a definitive not-found) OR if orgRateLimited is true. This prevents futile immediate retries against rate-limited endpoints.
4. Added a logger.debug call to the catch block to satisfy the no-silent-catch lint rule.

Verification:
Added a unit test to test/commands/event/view.test.ts to specifically cover the 429 rate-limit scenario, ensuring the organization is correctly excluded from the cross-org fallback.

Fixes CLI-2Y1

_{@sentry <feedback>: Autofix iterates on these changes
@sentry stop iterating: Autofix stops iterating on this run}

_{This PR was automatically generated by Sentry. You can adjust this setting at any time.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
cli	Ready	Preview	Sep 9, 2026 10:47am UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
sentry-local	Skipped		Sep 9, 2026 10:47am UTC