DashboardcliActive-token URL fallback

Active-token URL fallback

Category: architecture
Confidence: 1.00
ID: 01a08c1d-c76a-7f14-8daa-4c5f5d5f10d3
Project ID: c760f4f9-42b0-4ce0-b36d-6b8c38d770b2
Cross-project: No
Recalled in other projects: 0
Source session: 0yIbElBDrDPkcBsoR
Created: 2026-09-10 14:36:45
Updated: 2026-09-10 16:19:16

Content

Chose explicit configuration, then active-token host, then DEFAULT_SENTRY_URL for getApiBaseUrl() and getControlSiloUrl() over stored-OAuth region fallback because routing must follow auth precedence. Stored OAuth wins normally; when SENTRY_FORCE_ENV_TOKEN=1, the environment token’s sntrys_ claim wins and cached OAuth regions must never apply. Fetch-layer host guards still reject mismatched origins.

Move to: