Quick question about Data Action execution limits during load testing. We are running a JMeter script to simulate 100 concurrent inbound calls hitting a specific Architect flow. The flow triggers a custom Data Action that calls an external REST endpoint.
At around 40 concurrent users, the Data Action starts failing with a 504 Gateway Timeout. The external service logs show it received the request, but Genesys Cloud seems to drop the connection before the response is processed. The timeout is set to 30 seconds in the Architect configuration, which should be plenty for a simple JSON response.
Is there a hidden limit on concurrent Data Action executions per organization or per flow? The documentation mentions API rate limits, but this feels more like a connection pool exhaustion issue. We checked the WebSocket metrics, and they look stable.
Error details:
- Status: 504
- Component: Data Action Node
- Payload size: < 500 bytes
- Endpoint response time: ~200ms (verified via Postman)
Any ideas on how to tune this for higher throughput? We need to support at least 200 concurrent calls without these timeouts.