Just noticed that our custom Data Action integration starts failing with HTTP 429 Too Many Requests when the JMeter thread count exceeds 50 concurrent users. The endpoint is a simple GET request to our internal CRM API, configured via the Genesys Cloud Data Actions UI. The error occurs specifically during the initial burst of the load test phase, even though the target API has a rate limit of 1000 requests per minute. The Genesys Cloud logs show the request reaching the integration but returning the 429 status code before hitting our backend server.
The environment is Genesys Cloud US East (Virginia). We are using JMeter 5.6.2 with a thread group set to ramp-up over 5 seconds. The Data Action is configured with a timeout of 30 seconds. We have not configured any retry logic in the Architect flow yet, just a basic success/failure branch. The issue seems to be related to how Genesys Cloud handles concurrent outbound HTTP requests from the Data Action service. Is there a specific limit on concurrent Data Action executions per organization or per flow? We need to understand if this is a platform constraint or a misconfiguration in our load test setup.