Token refresh succeeds but 401s follow immediately

We’ve got a weird clock skew issue between our app server and Genesys. The refresh_token call returns a new access_token successfully, but the very next API request gets a 401 Unauthorized. The logs show the token is valid for 3600 seconds, so it shouldn’t be expired yet.

POST /api/v2/oauth/token
200 OK

GET /api/v2/interaction/interactions
401 Unauthorized
```"

Is there a way to force the server to ignore the slight time difference, or do I need to adjust the system clock on the integration box?