Running a JMeter 5.6 load test to validate Data Action throughput on Genesys Cloud US1. The goal is to simulate 150 concurrent API calls to a custom REST endpoint via Genesys Data Actions. After 5 minutes of steady state, getting 503 Service Unavailable errors on roughly 30% of requests. The target endpoint is healthy and can handle 500+ RPS independently.
Setup:
- JMeter 5.6 with HTTP Request Sampler
- Custom Data Action calling external HTTPS endpoint
- Thread Group: 150 threads, 5 min ramp-up, 10 min duration
- Genesys Cloud US1 environment
- Error occurs only during peak concurrency, not during ramp-up
The 503 errors include this response header:
X-Genesys-Trace-Id: abc123-def456
Retry-After: 5
Has anyone seen this specific behavior with Data Actions under high concurrency? Is there a hidden rate limit or capacity threshold for Data Action invocations that triggers 503s? Need to understand if this is a platform limitation or configuration issue before proceeding with production load testing. Appreciate any insights on Data Action capacity planning.