Does anyone know how to handle token refresh rate limits in load tests?
Running JMeter 5.6 against /oauth2/token on Genesys Cloud US1. Pushing 200 concurrent threads triggers HTTP 429 Too Many Requests immediately after initial auth. The environment uses standard security policies for API access. Need to validate throughput for high-volume agent login scenarios but getting blocked by rate limits on the auth endpoint. Config includes basic auth headers and standard grant type password flow. Error response shows retry-after header but JMeter does not handle it automatically in current setup.