Is it possible to bypass WebSocket limits during high-concurrency IVR load tests?

Architect & Flows
1

Is it possible to configure the Genesys Cloud environment to handle higher WebSocket connection counts during load testing? We are running a capacity test for a new IVR flow using JMeter. The goal is to simulate 500 concurrent callers hitting the main menu simultaneously.

The test fails consistently at around 150 concurrent connections. The flow itself is simple, just a menu selection and a transfer. However, the clients report connection drops.

Here is the error we see in the JMeter listener:

{
 "status": 429,
 "code": "too_many_requests",
 "message": "Rate limit exceeded for WebSocket connections"
}

We checked the API rate limits, but this seems different. The average throughput is low, but the instant spike causes the issue. Is there a setting in the Architect flow or the tenant configuration to increase the burst limit for WebSocket connections? We need to validate if the platform can handle the peak volume before go-live.

Any help is appreciated.

2

The best way to fix this is to check your jmeter thread group settings. you likely hit the api rate limit for websocket connections, not a hard platform cap. try staggering the ramp-up time instead of hitting 500 at once. also, ensure your virtual users are recycling connections properly in the script.