{"version":"2.0.53","anchor":"oauth-token-expiration-handling-for-usage-data","canonical_anchor":"oauth-token-expiration-handling-for-usage-data","heading":"OAuth Token Expiration Handling for Usage Data","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.0.53\/e\/oauth-token-expiration-handling-for-usage-data","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.0.53","markdown":"### OAuth Token Expiration Handling for Usage Data\n\n**What:** The API usage data fetcher now checks if the OAuth token is expiring before making API calls, gracefully falling back to cached data instead of throwing errors.\n\n**Details:**\n\n- Previously, the usage data fetch (`VPA()` at line 471623) would attempt API calls even with expiring tokens, potentially causing \"Failed to load usage data\" errors\n- Now checks if token expires within 5 minutes and returns `null` immediately if so\n- Falls back to cached usage data rather than displaying errors during token refresh windows\n- **Evidence**: `VPA()` at line 471623-471636 in v2.0.53, new check using `W6()` (OAuth token getter at line 163812) and `Ym()` (expiration checker at line 67497)\n\n**User impact:** Fewer transient error messages when viewing API usage near token expiration times."}