Stuck on a configuration issue with Genesys Cloud Data Actions. Trying to validate the throughput of a custom REST API integration under heavy load. The setup is simple: an Architect flow triggers a Data Action that calls an external endpoint.
When running JMeter 5.6 with just 20 concurrent threads, the flow hangs and eventually returns a 502 Bad Gateway error from the Genesys side. The external server logs show the requests are arriving fine, but Genesys seems to drop the connection or timeout.
Environment details:
- Genesys Cloud US1 environment
- JMeter 5.6 with HTTP Request Defaults configured for 10s timeout
- Data Action type: REST API (POST)
- Payload size: 2KB JSON
- Concurrent threads in JMeter: 20
The error happens consistently after about 30 seconds of load. I suspect there is a limit on how many concurrent Data Action executions Genesys allows per user or per flow, but I cannot find this documented clearly. The API logs in Genesys show the Data Action started but did not complete.
Is there a known limit on concurrent Data Action executions? Or is this a timeout configuration issue in the Architect flow settings? Any help on tuning this for higher concurrency would be appreciated.