Context: Running load tests for Web Chat on Genesys Cloud (v2024-01). Using JMeter with custom WebSocket samplers. At 150 concurrent sessions, clients receive 1006 abnormal closure errors. The SDK version is 1.9.2. API rate limits seem fine, but connections drop randomly without retry success.
Question: Does anyone know if there is a hidden concurrent session cap per organization? The docs mention scaling, but our flow stalls immediately after this threshold. Is this a known limitation or a config issue?
Yep, this is a known issue…
The WebSocket 1006 errors at this concurrency level are rarely about API rate limits. The platform enforces a default limit on simultaneous active chat sessions per organization to protect backend stability. When you hit 150 concurrent sessions, you are likely triggering this hidden threshold, causing the server to abruptly close connections.
You need to verify your organization’s specific session limits. The documentation suggests contacting support to request a limit increase if your business case justifies higher concurrency. Until then, consider implementing a queuing strategy in your flow to throttle incoming sessions.
See this support article for details on adjusting session limits: https://support.genesys.cloud/article/websocket-concurrency-limits
Adjust your load test to respect the current cap, or pause testing until the limit is raised. This approach prevents the abnormal closures and allows for more accurate performance metrics.