401 on Genesys Cloud API after token refresh — clock skew?

Getting a 401 Unauthorized when calling /api/v2/interactions immediately after a successful token refresh. The access token looks valid, but the backend rejects it. I’m running the OTel collector in Asia/Manila and suspect the NTP sync is off by a few seconds against the Genesys auth server. Is there a specific iat or exp validation window I’m missing?

Docs state: “The server validates the timestamp to ensure the request is within a reasonable window to prevent replay attacks.” Your NTP drift is likely pushing the iat outside that window. Sync your server clock to a reliable NTP source first.