JS SDK 401 post-refresh despite valid JWT nbf/exp

Hitting a 401 on /api/v2/analytic/conversations/summary right after the SDK auto-refreshes the token. The new token looks fine in the debugger, valid exp and nbf. But the server rejects it immediately. Suspect clock skew between my local machine and the GC auth server. The SDK uses Date.now() for the clock check, which is local. If my system clock is off by a few seconds, the token might be rejected by the backend before it’s technically valid, or the refresh happens too early/late.

// Token payload
{
 "iat": 1715420000,
 "exp": 1715423600,
 "nbf": 1715420000
}

// Error
{
 "code": 401,
 "message": "Unauthorized"
}

Is there a way to inject a custom clock or offset into the PlatformClient auth module? Or should I just sync my server time via NTP? The SDK doesn’t seem to expose a clock skew tolerance config.