Can anyone clarify the exact rate limit thresholds for the WFM schedule generation endpoints? Running a JMeter script to simulate high-volume schedule creation. The test hits POST /api/v2/wfm/scheduling/schedules with 100 concurrent threads. The goal is to measure system capacity under stress. However, after roughly 45 successful requests, the server starts returning 429 Too Many Requests. The response body contains a standard error message about exceeding rate limits, but no specific retry-after header value is present in the response headers.
The environment is a Genesys Cloud org in the US-East region. The JMeter config uses a constant throughput timer set to 50 requests per minute, but the burst at the start seems to trigger the limit. Is there a specific limit per organization or per user token for these endpoints? I suspect the default limit is quite low for admin API calls. Looking for any documentation on increasing this limit or best practices for pacing these requests. The current setup blocks the test execution completely after the first burst. Need to adjust the JMeter pacing strategy based on actual API limits.