Just noticed that the OAuth 2.0 token refresh endpoint returns HTTP 429 Too Many Requests when simulating 200 concurrent agents in JMeter. The standard rate limit for /oauth/token seems to be hit almost immediately as the load test scales up.
The test environment is Genesys Cloud v2, and we are using the standard client credentials flow. Each virtual user attempts to refresh the access token every 10 minutes to simulate a long-running session.
Is there a recommended backoff strategy or a way to batch these requests to avoid hitting the security gateway limits during performance baseline tests?