Is it possible to configure Genesys Cloud to handle higher throughput for custom Data Actions without triggering immediate 429 errors?
I am running a capacity validation test using JMeter 5.6 on the US1 environment. The goal is to simulate 150 concurrent agents invoking a specific Data Action via the Architect flow. The Data Action calls an external REST API to fetch customer data.
When the concurrent user count exceeds 50, the Architect flow starts failing with a 429 Too Many Requests error. The response headers indicate the limit is being hit quickly. I have checked the standard API rate limit documentation, but it is not clear if Data Actions share the same pool as standard REST APIs or if they have a separate dedicated capacity.
The JMeter configuration uses a simple loop controller with a 2-second constant timer between requests. The external API responds in under 200ms, so the bottleneck seems to be on the Genesys Cloud side.
Is there a way to increase the throttle limit for specific Data Actions, or is this a hard cap for our current subscription tier? I need to validate if our architecture can support the peak volume expected next month. Any guidance on configuring the Data Action timeout or retry logic in Architect would also be appreciated.