Can anyone clarify the expected behavior of OAuth token refresh when running high-concurrency load tests against Genesys Cloud platform APIs?
We are running JMeter 5.6.2 from a Singapore-based instance to simulate extreme API throughput against our BYOC Edge 24.1.0 environment. The goal is to validate system stability under heavy concurrent request loads, specifically targeting the /api/v2/interactions endpoints.
The issue arises when we ramp up to 200 concurrent threads. Initially, the client credentials grant flow works fine. However, as the initial tokens begin to expire (after 1 hour), the JMeter script attempts to refresh them. We start seeing a significant spike in 401 Unauthorized errors, not just for the refresh endpoint itself, but for subsequent API calls that rely on the new tokens. It seems like the token refresh mechanism is either rate-limited more aggressively than the standard API calls or there is a race condition where threads are using expired tokens while waiting for the refresh to complete.
Is there a specific header or parameter we need to adjust in the JMeter HTTP Request Defaults to handle this token lifecycle correctly during a load test? Or is this a known limitation of the platform API under high concurrency?