Just noticed that custom data actions fail with a 504 Gateway Timeout when JMeter hits 200 concurrent threads. The endpoint is /api/v2/data/actions. The underlying service responds fine at low volume. Is there a specific WebSocket limit or API rate cap for data actions in US1? Checking Genesys Docs but unclear on burst thresholds. Need to validate capacity for peak IVR load.
This is a standard burst limit issue rather than a WebSocket constraint. The WFM API handles bursts differently than data actions.
504 Gateway Timeout
Consider implementing exponential backoff in your JMeter script. The default rate limits for /api/v2/data/actions are strict during peak hours. Check the X-RateLimit-Remaining header to tune your thread pool size.
"timeout_ms": 30000 in the data action definition fixed it for us. In Zendesk, custom actions were just simple macros, but GC treats these as long-running tasks that need explicit timeout configuration. Check the Data Actions API docs for the exact field mapping.