What is the standard approach to handle rate limiting when querying WFM adherence data at scale?
Running JMeter from Singapore. Targeting Genesys Cloud API v2. Simulating 200 concurrent adherence checks for agents. Hitting /api/v2/wfm/scheduling/adherence. Getting 429 Too Many Requests immediately after ramp-up.
The response headers show Retry-After: 5. My test plan uses a constant throughput timer set to 50 req/sec. The load spikes hit the limit fast. Need to validate bulk adherence fetch logic for a large contact center migration. Current setup fails before hitting 10% of total target volume.
- Added exponential backoff in JMeter BeanShell PostProcessor. Retries delay by 2 seconds. This slows the test but still hits 429 errors on peak load.
- Tried batching requests using
/api/v2/wfm/scheduling/adherence/bulk. The endpoint returns 501 Not Implemented for some tenant configurations. Documentation is unclear on bulk support for adherence vs schedules.