What’s the best way to handle Data Action timeouts during JMeter load test?
Running JMeter 5.6 with 200 concurrent users against a custom Data Action in Genesys Cloud US1. The action calls an external REST API via the HTTP client block. When concurrency hits 150 req/s, the Architect flow returns HTTP 504 Gateway Timeout. The error happens at the HTTP request step inside the Data Action. Standard flow works fine at lower concurrency.
The external endpoint responds in under 200ms at low load. The timeout seems to occur on the Genesys Cloud side before reaching the external system. The Data Action timeout is set to 30 seconds. The HTTP client timeout is set to 10 seconds. The Architect flow timeout is set to 60 seconds.
Is there a rate limit for Data Action invocations per second? Are there specific capacity limits for HTTP client blocks in Data Actions? How should the timeout values be configured to avoid 504 errors during peak load? Any guidance on scaling Data Actions for high throughput would be helpful.