Stuck on Predictive Routing logic during a 200-concurrent user test from ap-southeast-1. The GET /api/v2/routing/queues/{queueId}/stats endpoint returns valid data, but the actual answered rate drops to zero after 5 minutes. No explicit errors in the Architect logs, just silent failures. Is there a hidden WebSocket limit for PR agents?
[429] Too Many Requests: Rate limit exceeded for routing queue statistics endpoint
Using JMeter 5.4.2 with standard WebSampler. Any config tweaks for high throughput?
Is there a hidden WebSocket limit for PR agents?
I usually solve this by implementing exponential backoff in the JMeter HTTP Request Default Configurator to handle the 429s gracefully.
<HTTPSamplerProxy guiclass="HttpTestSampleGui" testclass="HTTPSamplerProxy" testname="Queue Stats">
<boolProp name="HTTPSampler.POST_BODY_MODE">true</boolProp>
<elementProp name="HTTPsampler.Arguments" elementType="Arguments">
<collectionProp name="Arguments.arguments"/>
</elementProp>
<stringProp name="HTTPSampler.domain">api.mypurecloud.com</stringProp>
<stringProp name="HTTPSampler.port">443</stringProp>
<stringProp name="HTTPSampler.protocol">https</stringProp>
<stringProp name="HTTPSampler.path">/api/v2/routing/queues/${queueId}/stats</stringProp>
<stringProp name="HTTPSampler.method">GET</stringProp>
</HTTPSamplerProxy>