Stuck on understanding why the Workforce Engagement Management endpoints are throttling so aggressively during our automated load tests. We are running JMeter 5.6.2 from our Singapore lab against a Genesys Cloud BYOC Edge 24.2 environment. The specific issue occurs when hitting POST /api/v2/wfm/schedules/query with just 15 concurrent threads. The response returns a 429 Too Many Requests error almost immediately, even though the request payload is minimal and valid JSON.
This is confusing because the Analytics API seemed to handle similar concurrency better in previous tests. We are trying to establish a baseline for schedule retrieval performance under load, but the rate limiting feels inconsistent with documented limits for our tier.
- Verified the OAuth token is valid and not expiring mid-test. Used the same token generation script as previous successful API tests.
- Checked the WEM API documentation for specific rate limits on schedule queries. No explicit limit mentioned for this endpoint other than general platform constraints.
Any insights on how to tune JMeter thread groups or if there is a hidden rate limit for WEM endpoints in the Asia/Pacific Southeast region? Need to get this baseline data before the next sprint review.