Transparent token refresh
Auto-generated from the source archive. Do not edit by hand — rerun
catalyst-changelog-syncinstead.
What changed
Section titled “What changed”- When an in-page GraphQL operation fails with
UNAUTHENTICATEDbecause the access token expired, the Apollo error link now transparently callssignInUsingRefreshToken()and retries the original operation instead of redirecting to sign-in. - Concurrent 401s share a single in-flight refresh, each operation retries at most once, and only user operations trigger it. Sign-in happens only when the refresh itself is unavailable or fails (
invalid_grant).
Why it matters
Section titled “Why it matters”Access tokens last about an hour and refresh tokens about a month, but previously any access-token expiry kicked the user back to the login screen on the next navigation — even though the refresh token was still valid — forcing a re-login roughly every hour for no reason. Sessions now stay alive silently up to the refresh-token lifetime.