Why does this setting… cause the Architect flow to crash when we push concurrent sessions past 50?
Running a load test against a simple IVR menu in Genesys Cloud (ap-southeast-1). Using JMeter to simulate inbound calls via the Media API. The flow just has a “Get Digits” block followed by a “Play Prompt”.
At 10 concurrent threads, everything works fine. Latency is low. But when I ramp up to 50 threads, I start seeing intermittent 503 Service Unavailable errors from the Architect engine. The WebSocket connection stays alive, but the message events stop flowing.
Checked the logs. No obvious errors on the server side. Just timeouts. Is there a default concurrency limit on the Architect engine for free-tier or dev tenants? Or is this a known bottleneck with the Media API in this region?
JMeter config:
- HTTP Request Defaults: Genesys Cloud Base URL
- Thread Group: 50 threads, 0 ramp-up, 1 minute loop
- Sampler: WebSocket connection to media server
Need to know if this is a config issue or a platform limit before we scale further.
Why does the Architect flow return 503 errors when concurrent sessions exceed 50 in ap-southeast-1, and is there a way to increase this limit?