Need some help troubleshooting… The custom IVR flow in Genesys Cloud Architect is timing out when JMeter threads exceed 200. Running JMeter 5.6.2 from Singapore. Targeting 200 concurrent softphone connections. Hitting 504 Gateway Timeout on the /api/v2/architect/flow/execute endpoint.
The flow is pretty simple. Just a greeting, a menu selection, and a transfer to a queue. No complex Data Actions or external API calls. Just standard Architect nodes. The issue starts exactly at thread 201. Threads 1-200 work fine. Thread 201 gets the 504 error immediately. No retry logic helps.
Environment details:
- Genesys Cloud Environment: Production (Singapore region)
- JMeter Version: 5.6.2
- Test Location: Singapore (AWS ap-southeast-1)
- Concurrent Threads: 200 (ramp-up 10/sec)
- Flow ID: 8a1b2c3d-4e5f-6a7b-8c9d-0e1f2a3b4c5d
- Queue ID: 1a2b3c4d-5e6f-7a8b-9c0d-1e2f3a4b5c6d
The logs show the WebSocket connection is established. The initial handshake succeeds. But the flow execution never completes. It just hangs until the 504 timeout. Checked the Architect flow logs. No errors there. Just missing entries for the failed threads.
Could this be a rate limit issue? Or a WebSocket connection limit per tenant? The API docs mention rate limits for /api/v2/oauth/token but nothing specific for Architect flow execution. The /api/v2/architect/flow/execute endpoint is used internally by the softphone client. Not sure if there are hidden limits.
Tried increasing the JMeter ramp-up time. No change. Tried reducing the concurrent threads to 150. Works fine. Increased to 180. Works fine. 200 is the hard limit. 201 fails every time.
Any ideas? Is there a way to increase the flow execution capacity? Or is this a known limitation in the Singapore region? The latency to the Genesys Cloud servers is low (10ms). Network is not the issue.
Thanks for any input.