Trying to understand why our bot capacity limits are hitting 100% immediately after the Tuesday WFM schedule publish in Chicago. The Architect flow for IVR routing seems to ignore the updated agent availability from the WFM integration. We are seeing a 503 Service Unavailable when querying the agent schedule generation unavailable times right after the publish completes. The bot queue is backing up while agents are technically online but not routing. Using Genesys Cloud API v2.150.0. Is there a known latency between WFM publish and bot capacity recalculation?
this looks like a rate limit issue. the wfm publish triggers a burst of api calls that exhausts the bot capacity before the schedule updates propagate. add a 5s delay in your jmeter test to avoid hitting the 503.