Can anyone explain why the Architect flow is returning a 504 Gateway Timeout when I simulate 150 concurrent users via JMeter 5.6? The flow is simple: a single “Get User Input” block with a 10-second timeout, followed by a “Set Variable” and “Hangup”. No complex logic or external API calls.
The environment is Genesys Cloud US1. I am using the standard WebSocket connection for the softphone simulation. When concurrency is low (under 50 threads), it works fine. But once I hit 100+ threads, the success rate drops to 40%. The error appears in the JMeter response as a connection reset after the 10-second input timeout.
I checked the Architect Capacity Limits doc, but it does not mention specific WebSocket handshake limits for incoming calls. Is this a platform-side throttling issue or a misconfiguration in my load test script? I have attached the JMX file structure in my notes if needed. Any advice on how to tune the thread group or if there is a hidden rate limit on call initiation?