Just noticed that our Architect flow starts failing with HTTP 503 Service Unavailable when JMeter hits 200 concurrent threads on POST /api/v2/architect/flows. The flow uses a Data Action to fetch customer info from our backend. Latency spikes to 5 seconds before the error. We are on Genesys Cloud US1 region. Is there a specific rate limit for Data Actions or should we increase timeout? JMeter shows success until this threshold.
The root of the issue is that the Data Action timeout is too low for the observed latency. Increase the HTTP timeout to at least 10 seconds in the Data Action configuration, as the default 30-second limit is for the entire execution, not just the external call.