Stuck on handling 429 Too Many Requests when simulating high-concurrency requests to the Workforce Management Forecast API.
Environment: Genesys Cloud US1
Tool: JMeter 5.6
Endpoint: /api/v2/wfm/scheduling/forecasts
The test scenario involves loading forecast data for 500 concurrent users. The 429 errors start appearing after approximately 500 requests per second. The response headers indicate the rate limit is exceeded, but the standard retry logic with exponential backoff is not sufficient to maintain the desired throughput.
Is there a way to configure higher rate limits for the WFM Forecast API during load testing? Or are there specific best practices for handling rate limiting in JMeter scripts for this endpoint? The goal is to validate system capacity for forecast data loading during peak planning hours.
Any advice on adjusting the JMeter configuration or API usage patterns would be appreciated.