What’s the best way to handle WebSocket connection drops when simulating high concurrent call volumes in Architect flows? The environment is US1. Using JMeter 5.6 with Genesys Cloud SDK 2.3.0.
The test scenario involves a simple IVR flow with a single “Play Text” node. When concurrent sessions exceed 50, the WebSocket connections begin to fail intermittently. The logs show 1006 abnormal closure codes. This happens before any API rate limits are hit.
Steps to reproduce:
- Configure JMeter thread group for 60 concurrent users.
- Each user initiates a call via the Pure Cloud API.
- Monitor the WebSocket connection status in the Architect flow.
- Observe connection drops after 30 seconds of activity.
The goal is to validate system stability under load. Need to understand if this is a client-side timeout issue or a server-side capacity limit. Any guidance on adjusting timeout settings or handling reconnections in the SDK would be appreciated.