- Error 429 Too Many Requests returned by
/api/v2/wfm/scheduling/shiftrequests endpoint when executing JMeter test plan.
- Environment: Genesys Cloud US1 region. JMeter version 5.6.1 running on local Windows machine (America/New_York timezone).
- Test scenario involves simulating bulk shift request submissions for workforce management validation.
- Initial configuration uses 50 concurrent threads with a ramp-up period of 10 seconds.
- Request body contains standard shift request JSON payload with
start_time, end_time, and userId fields.
- Authentication handled via OAuth 2.0 client credentials flow with token refresh logic implemented in JSR223 pre-processor.
- First 20 requests succeed with 200 OK status and return expected shift request objects.
- Subsequent requests fail immediately with 429 status code and response body indicating rate limit exceeded.
- Retrying requests after 5-second delay results in same error, suggesting persistent throttling rather than temporary spike.
- Checked documentation for WFM API rate limits but found conflicting information regarding burst capacity.
- Current assumption is that default tenant limit is 100 requests per minute for this specific endpoint.
- Attempted to reduce concurrency to 10 threads with 1-second constant throughput timer.
- Results show improved success rate but still hit 429 errors after approximately 80 total requests.
- Monitoring Genesys Cloud admin dashboard shows no visible throttling warnings or alerts during test execution.
- Question focuses on identifying correct rate limit thresholds for WFM scheduling APIs under load.
- Seeking advice on proper pacing strategies or exponential backoff implementation in JMeter for WFM endpoints.
- Also interested if there are specific headers or parameters to include for higher throughput allowances.
- Previous load tests on IVR and messaging channels showed different error patterns (403, 504) but WFM behaves differently.
- Need to validate system capacity for end-of-month shift planning peaks which involve high concurrent user activity.
- Any insights from other load testing engineers regarding WFM API scaling limits would be helpful.