Stumbled on a weird bug today with the HTTP POST data action in Architect. It works fine for low volume but fails when JMeter hits 100 concurrent users.
The error is a 504 Gateway Timeout on the internal connector. The target API is responding in 200ms, so the issue seems to be on the Genesys Cloud side.
Any config changes needed for high throughput data actions?
Make sure you set timeout to 60000 in the data action config. The default 30s limit gets crushed by latency spikes when JMeter ramps up threads.
It depends, but generally…
Setting the timeout is necessary, but the connector pool size often bottlenecks before the timeout triggers. The default pool limits concurrent outbound calls per tenant.
Check these:
- Data action concurrency limits
- Target API rate limits
- Genesys Cloud connector pool configuration