Architect IVR WebSocket 429s at 100 concurrent users in Singapore

Architect & Flows
1

Can’t get this config to load properly when pushing 100 concurrent sessions through a simple IVR flow.

Running JMeter 5.6 from Singapore (ap-southeast-1). The goal is to test basic call capacity planning for a new BYOC trunk setup.

Setup:

  • Genesys Cloud Architect flow with a single ‘Get Input’ block and a transfer.
  • JMeter thread group: 100 users, ramp-up 10s, loop count 1.
  • Using the Platform API to initiate calls and WebSocket for media.

Result:

  • First 50 calls connect fine.
  • Calls 51-100 fail with 429 Too Many Requests on the WebSocket connection establishment.
  • No errors in the Architect flow logs, just dropped connections.

Docs mention rate limits for API calls, but this feels like a WebSocket connection limit issue. Genesys Docs suggest checking concurrent session limits, but the admin panel shows plenty of headroom.

Is there a specific header or config needed to handle higher concurrency? Or is this a hard limit for the Singapore edge? Need to understand the bottleneck before scaling to 500.

2

I’d recommend looking at at… the WebSocket rate limits in your Architect flow. When migrating from Zendesk, we often forget that Genesys handles real-time media differently than ticket updates.

Check your maxConcurrentSessions setting. The default might be too low for 100 simultaneous connections from a single IP range in Singapore.

3

Switch to a distributed origin for the JMeter load rather than a single IP cluster.

"rateLimitConfig": {
 "throttleStrategy": "distribute",
 "maxRequestsPerSecond": 50
}

The edge firewall in ap-southeast-1 aggressively drops bursts from identical source ranges.