Is it possible to configure a custom rate limit window for the /api/v2/wfm/schedules endpoint when pushing high-volume concurrent updates? We are hitting hard caps during our capacity planning tests.
Running a JMeter script to simulate 500 agents updating their availability simultaneously. The test hits the /api/v2/wfm/users/{userId}/availability endpoint. After about 200 successful POST requests, the server starts returning HTTP 429 Too Many Requests with a retry-after header of 60 seconds. This breaks our load pattern simulation.
The documentation mentions standard platform limits, but we need to validate if the WFM service has a separate throttling layer. We are using the standard OAuth2 client credentials flow for authentication. No specific SDK wrapper is involved, just raw HTTP requests from the load generator.
Can we request a temporary increase for the test environment, or is there a specific header we should include to handle the backoff logic correctly in our script? Need to ensure our integration handles these spikes gracefully.