Could someone explain why I am receiving a 401 Unauthorized response from the Genesys Cloud API immediately after a successful token refresh operation? I am developing an enterprise Angular agent desktop using the GC Premium App framework. The application uses an Angular service to manage OAuth tokens via RxJS. When the access token expires, the refreshAccessToken method is triggered. The refresh request returns a 200 OK with a new access token and expires_in value. However, the subsequent API call to /api/v2/users/me fails with a 401. I suspect a clock skew issue between the client machine and the Genesys Cloud servers. The client system time is synchronized with America/Chicago NTP servers. The JWT payload contains an iat claim that appears to be slightly ahead of the server’s expected window. Is there a specific header or configuration in the SDK to adjust for this skew? Or should I implement a manual clock drift calculation in the refresh logic? The error response body is minimal, providing no additional context. I have verified the token validity using external JWT decoders. The token is valid according to the claims. Yet the API rejects it. This issue occurs intermittently, suggesting a timing dependency. Any insights on how to handle this in the Angular service layer would be appreciated.