Is it possible to configure a higher throughput for the Workforce Management APIs?
I am running a JMeter script against Genesys Cloud BYOC Edge 24.1.0. The environment is in Asia/Singapore. The goal is to simulate a sudden spike in scheduling requests. This mimics a scenario where many agents update availability simultaneously.
The test hits POST /api/v2/wfm/scheduling/schedules. I am using JMeter 5.6.2. The thread group starts with 50 threads. The ramp-up period is set to 10 seconds. Each thread sends a request every 200 milliseconds.
The API returns 429 Too Many Requests immediately. The response header shows Retry-After: 5. This kills the throughput. The test fails after just 12 seconds.
I checked the API documentation. It mentions standard rate limits for WFM endpoints. I do not see a way to increase this via the portal. There is no X-RateLimit-Reset header in the response. This makes it hard to implement a proper backoff strategy in JMeter.
My JMeter config uses HTTP Request samplers. I am not using any custom plugins. The payload is minimal. It contains just the scheduleId and the time slot data. The size is under 1KB.
Is there a specific header I should add? Maybe X-Genesys-Request-Id? I read something about that in the platform API docs. Or is WFM strictly capped regardless of the request type?
I tried adding a Constant Timer. I set it to 1000ms delay. The 429 errors still occur. This suggests the limit is very low. Maybe 1 request per second per tenant?
I need to validate the system capacity. The current limits seem too restrictive for a load test. I cannot simulate realistic peak loads.
Any advice on how to handle this? Should I switch to batch endpoints? I see POST /api/v2/wfm/scheduling/schedules/bulk. Does that have different limits?
The environment details are consistent with my previous posts. BYOC Edge 24.1.0. Asia/Singapore region.
I am new to WFM APIs. I usually work with Conversations or Outbound. The rate limiting behavior seems different here.
Please share any JMeter scripts or configurations that work. I need to get past this wall. The test is stuck at 10 RPS. The target is 500 RPS.
Thanks for any help.