Could someone clarify why the custom Data Action is timing out under load?
Running JMeter 5.6.2 from Singapore (Asia/Singapore). Simulating 200 concurrent requests hitting a custom Data Action via Genesys Cloud Architect. The endpoint is /api/v2/integrations/external/dataactions.
At low concurrency (10 users), the response time is ~150ms. But when I ramp up to 200 users, I start getting 504 Gateway Timeout errors after 30 seconds. The external service is returning 200 OK within 50ms, so the bottleneck seems to be on the Genesys side or the connection pool.
JMeter Config:
- Thread Group: 200 threads, 0 ramp-up, 60 duration
- HTTP Request Defaults: Timeout 30000ms
- No delays between requests
Checked the Data Action Limits page but it doesn’t specify a concurrent execution limit per tenant. Is there a hidden queue depth limit? Or is this a WebSocket connection issue?
Logs show the request reaches the external server but Genesys drops the connection before the response is processed. Any ideas on how to increase the timeout or handle this better?