{"version":"2.1.71","anchor":"client-data-fetching-system-gradual-rollout","canonical_anchor":"client-data-fetching-system-gradual-rollout","heading":"Client Data Fetching System [Gradual Rollout]","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.71\/e\/client-data-fetching-system-gradual-rollout","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.71","markdown":"### Client Data Fetching System [Gradual Rollout]\n\n**What**\n\nA new `clientData` fetching system that pulls configuration and feature data from the server at session start, with caching, retry logic, and 401 token refresh.\n\n**Status**\n\nFeature-flagged \u2014 appears to require OAuth subscriber status with specific profile scopes.\n\n**Details**\n\n- Fetches client data on session start with exponential backoff retries\n- Caches responses to disk; skips writes if unchanged\n- Handles 401 by refreshing OAuth tokens and retrying\n- Skipped when \"nonessential traffic\" is disabled or when user lacks the required OAuth scopes\n\n**Evidence**\n\nClient data infrastructure (search for `\"[clientData] fetch ok\"`)"}