Data Action 502 Bad Gateway during high-concurrency load test

HTTP 502 Bad Gateway

Running a load test from Singapore using JMeter 5.6.2. Target is Genesys Cloud platform_api. The script triggers a custom Data Action via an Architect flow. At 50 concurrent threads, the HTTP request sampler fails consistently.

The Data Action calls an external REST endpoint. The external endpoint is healthy. Latency is low. The issue appears on the GC side. The error occurs after the WebSocket connection is established. The flow logs show the Data Action timeout.

JMeter config:

  • Thread Group: 50 threads
  • Ramp-up: 5 seconds
  • Loop Count: 10
  • Timeout: 30 seconds

The platform_api documentation mentions rate limits. But 50 threads is below the standard limit. The 502 error suggests a proxy or gateway failure. Not a rate limit 429. Not a 500 Internal Server Error.

Is there a specific limit on Data Action executions per second? Or is this a known issue with high-concurrency flows in the Singapore region? The load pattern is steady. No spikes. Just consistent failure at the gateway level.

Need to validate if this is a configuration error or a platform constraint. Any insights on handling this in load tests?