401 Unauthorized after token refresh due to clock skew?

Our Node.js backend is hitting 401s immediately after a successful token refresh via the genesys-cloud/purecloud-platform-client-v2 SDK. The logs show the new access token is valid, but the Genesys Cloud API rejects it with invalid_grant or expired claims. Checked the server time and it’s synced, but I suspect a subtle clock skew between our load balancer and the Genesys auth endpoint is breaking the exp validation window. Anyone seen this with the JS SDK?