{"version":"2.1.271","anchor":"oauth-token-refresh-now-skipped-by-default-unless-first-part","canonical_anchor":"oauth-token-refresh-now-skipped-by-default-unless-first-part","heading":"OAuth token refresh now skipped by default unless first-party or forced","tier":"internal","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/oauth-token-refresh-now-skipped-by-default-unless-first-part","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### OAuth token refresh now skipped by default unless first-party or forced\n\nOAuth token refresh is now skipped by default unless required or forced\n\n**Unclear.** Whether this behaves differently for any accounts is unclear, since the related gate is unread for this release.\n\n**What**\n\nThe function that refreshes OAuth authentication tokens now takes a new trailing parameter, off by default. After confirming a refresh token exists and can be refreshed, it now returns \"not needed\" and skips the refresh unless a condition function says it's required or the new parameter forces it.\n\n**Why**\n\nThis avoids unnecessary token refresh calls in cases where refreshing isn't actually needed.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}