Stuck on a problem and need help troubleshooting a rate limiting issue with the Workforce Management API. I am running a basic load test to check capacity for shift request submissions. The target endpoint is /api/v2/wfm/scheduling/shiftrequests. I am using JMeter 5.6 with a simple HTTP Request sampler. The test plan uses 20 concurrent threads with a ramp-up period of 5 seconds. Each thread loops 10 times. The environment is Genesys Cloud US1.
The test starts fine. For the first few seconds, I see 200 OK responses. Then, almost immediately, the responses switch to 429 Too Many Requests. This happens even though I am using a valid OAuth 2.0 token. The token is generated once before the test starts and is valid for a long time. I am not hitting the global API limit for the org. I checked the admin portal. The usage is low. So, this must be a specific limit for the WFM scheduling endpoints.
“Rate limits for WFM scheduling APIs are enforced per tenant and per endpoint. High concurrency can trigger temporary blocks.”
This quote is from the Genesys Cloud Developer documentation. It does not give the exact number of requests per minute allowed. I need to know this number to adjust my JMeter config. Is there a way to see the current rate limit status in the response headers? I looked at X-RateLimit-Remaining but it is not always present. Sometimes it is missing. This makes debugging hard.
I tried adding a random pause of 100ms between requests. This helps a little. But the 429 errors still appear. I want to understand the exact limit. Is it 60 requests per minute? Or is it lower? I also tried splitting the load across multiple tokens. This did not help much. The errors persist. I suspect the limit is very strict for this endpoint. Can anyone share the specific rate limit values for /api/v2/wfm/scheduling/shiftrequests? I need accurate numbers for my capacity planning report. The client wants to know how many agents can submit shifts at the same time. My current setup fails at 20 threads. This seems low. Is this expected behavior? Genesys Cloud. I have only been working with the platform for one year. I usually focus on voice traffic. WFM is new for me. Any advice on how to structure the JMeter test to avoid these errors would be appreciated. I can share the JMX file if needed.