{"version":"2.1.269","anchor":"policy-limits-fetch-now-retries-once-after-a-401-with-a-forc","canonical_anchor":"policy-limits-fetch-now-retries-once-after-a-401-with-a-forc","heading":"Policy limits fetch now retries once after a 401 with a forced token refresh","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/policy-limits-fetch-now-retries-once-after-a-401-with-a-forc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Policy limits fetch now retries once after a 401 with a forced token refresh\n\nPolicy limits requests now retry once with a forced token refresh after a 401 error\n\n**What**\n\nThe request that fetches policy limits now goes through a wrapper that can force a refresh of the OAuth authentication token and retry the request if it first fails with a 401 (unauthorized) error. Every result returned now also carries a `retriedAfter401` flag indicating whether this retry happened.\n\n**Why**\n\nThis should reduce spurious failures when fetching policy limits with an expired token, by automatically refreshing the token and retrying once instead of surfacing the authentication error.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}