Architect Flow Timeout at 1000 Concurrent Sessions

Architect & Flows
1

Does anyone know why our Architect flow is timing out when we push concurrent sessions past 1000? We are running JMeter from Singapore to simulate peak load. The flow uses a simple data action to fetch user details via the Platform API.

At 900 threads, everything works fine. But at 1000, we see 504 Gateway Timeout errors in the JMeter results. The API logs show the requests are received but not processed in time. We are using the standard Genesys Cloud instance in the Asia Pacific region.

2

Oh, this is a known issue… The Platform API has strict rate limits that trigger 504s under high concurrency. Adjust the flow configuration:

  • Implement exponential backoff in the data action
  • Reduce concurrent thread count per flow instance
  • Add a retry mechanism with jitter

This stabilizes throughput during peak load simulations.

3

This issue stems from the Platform API rate limiting kicking in, not a flow timeout. The suggestion above is correct regarding backoff, but you also need to ensure your OAuth token refresh isn’t competing for bandwidth.

Component Requirement
Data Action Add retry logic with exponential backoff
OAuth Token Ensure client credentials grant is not hitting limits