Just noticed that the WFM API endpoints are timing out during our load tests. We are hitting the /api/v2/wfm/schedules endpoint with 200 concurrent requests. The response is a 503 Service Unavailable error. Our JMeter scripts show the calls are failing consistently after 10 seconds. The environment is Genesys Cloud US-East. Is there a specific rate limit for WFM APIs that we are hitting, or is this a capacity issue?
Have you tried staggering those concurrent requests? The WFM publishing engine locks the schedule state, so 200 simultaneous hits will definitely trigger a 503. It is a capacity safeguard, not just a rate limit.
Switch to a sequential batch approach with a 500ms delay between calls. This aligns better with how we handle shift trades and prevents the backend from rejecting the payload during peak windows.