Anyone know why the Architect flow is returning a 504 Gateway Timeout when JMeter 5.6 pushes 150 concurrent sessions to the US1 region? The flow is simple, just a DTMF gather followed by a transfer to a queue. The issue happens after about 45 seconds of idle time in the gather step. We are using the standard WebSocket connection for the load test. The error appears in the JMeter response as a timeout, but the Genesys Cloud logs show the session is still active. We tried increasing the timeout in the flow to 60 seconds, but the 504 still occurs at the 45 second mark. The API rate limits are not being hit, as we are only making one initial connection per thread. The environment is US1, version is current. We need to know if there is a hidden session timeout for gather steps under load or if this is a bug in the load testing simulation. The JMeter config uses the HTTP Request sampler with WebSocket upgrade. We are not seeing this issue with 50 concurrent users. It only starts failing at 100+. Is there a limit on concurrent active flows per tenant? We checked the admin console and the capacity seems fine. Please help.