Rotating Genesys Cloud OAuth client secrets without downtime?

Hey folks,

Trying to rotate client secrets for our integration without dropping active sessions. The docs mention generating a new secret, but I’m not seeing a clear sequence for swapping them in the SDK config without a full restart.

If I update the secret in the portal, do existing tokens stay valid? Or do I need to handle the 401 Unauthorized errors in my retry logic?

POST /oauth/token
401 Unauthorized: invalid_client

Any tips on handling the transition window?