HTTP 429 Too Many Requests is returned by the Genesys Cloud API when simulating high-frequency availability checks via JMeter 5.6. The target environment is US1. The goal is to validate system stability under load for agent availability updates, not to bypass limits. However, the rate limiting is triggering immediately, preventing accurate performance measurement of the WFM integration layer.
Steps to reproduce:
- Configure JMeter with 50 concurrent threads.
- Set up an HTTP Request sampler targeting
GET /api/v2/wfm/scheduling/groups/{groupId}/availability. - Execute the test plan with a ramp-up period of 10 seconds.
- Observe the response codes. Most requests return 429 after the first 5-10 successful calls.
The headers show Retry-After: 10. As a load testing engineer new to Genesys Cloud, I need to understand if this is a hard limit for WFM endpoints specifically, or if there is a configuration setting in the tenant to adjust burst capacity for testing purposes. Standard REST API rate limits are documented, but WFM specific limits are unclear. Is there a recommended pattern for load testing WFM APIs without hitting these limits instantly?