Is it possible to bypass Architect IVR rate limits during JMeter load test? Running JMeter 5.6 against the IVR entry point to simulate high concurrent call volumes. The goal is to test Genesys Cloud call capacity planning. Getting 429 Too Many Requests when simulating 100 concurrent users in US1. The limit seems much lower than standard documentation suggests. The error appears immediately after the first 50 calls. No WebSocket connection issues observed. Just API throttling on the IVR trigger.
The test plan uses a simple Thread Group with 100 threads, ramp-up 0, loop count 1. Each thread initiates a call via the conversations API. The IVR flow is basic: play prompt, collect DTMF, route to queue. No complex logic. The bottleneck is clearly at the entry point, not the routing logic.
Environment: Genesys Cloud US1, JMeter 5.6, Architect v2023.10.
Has anyone seen this behavior? Is there a specific header or configuration to increase the limit for testing purposes? Or is this a hard limit for IVR triggers? Need to understand the true concurrent call volume capacity before production rollout. Any insights on how to properly stress test IVR entry points without hitting immediate throttling?