Could someone explain why I am hitting 429 Too Many Requests errors so early when testing the Workforce Management API? I am running a simple JMeter script from Singapore to simulate agents checking their availability status via GET /api/v2/wfm/schedule/agent/{agentId}.
The setup is basic. One thread group, ramp-up of 1 second, and I am trying to reach just 20 concurrent users. The goal is to see how the API handles sudden spikes in load during shift changes. The docs mention rate limits, but I assumed 20 requests per second would be well within the safe zone for a standard tenant.
Here is what happens:
- Thread count reaches 10.
- First few requests return 200 OK.
- Suddenly, almost all subsequent requests fail with 429.
- The
Retry-Afterheader suggests waiting 30 seconds.
I have checked my OAuth token scopes, and wfm:admin is definitely included. The endpoint itself seems correct based on the Genesys Docs.
Is there a specific limit for this endpoint that I missed? Or does the load test pattern itself trigger a protection mechanism? I am new to this platform, so I might be misunderstanding how the rate limiting works for WFM endpoints compared to other APIs.