How should I properly to structure the API calls for Workforce Management scheduling when running a JMeter load test? We are trying to simulate a high volume of shift trade requests to see how the system handles concurrent updates. Currently, we are hitting the /api/v2/wfm/scheduling/shifttrades endpoint with 50 threads ramping up over 10 seconds on the US1 environment. The test fails almost immediately with 429 Too Many Requests errors, even though we are using valid OAuth tokens and the payload is minimal. We want to know if this is a hard limit on the WFM service or if our thread group configuration in JMeter is too aggressive for this specific API family.
The response headers indicate a retry-after time of 5 seconds, which slows down the entire test scenario significantly. We are using Genesys Cloud version 2024-02 and JMeter 5.6.2. Is there a recommended pattern for batching these requests or a specific rate limit documentation for WFM shift trade APIs that we are missing? We need to determine the actual throughput capacity of this endpoint under stress to plan our scaling strategy, but the current 429 errors prevent us from gathering meaningful latency data.