Just noticed that the NLU intent update endpoint is returning 429 Too Many Requests errors when we ramp up the thread count in JMeter. We are trying to simulate a high-frequency training data push scenario from our Singapore office. The target endpoint is /api/v2/bots/nlu/intents.
Our current JMeter config uses 50 concurrent users with a 5-second ramp-up, hitting the endpoint every 2 seconds per thread. The error starts appearing almost immediately after the ramp-up completes. The response header indicates the retry-after value is 60 seconds, which breaks our test flow completely. We checked the Genesys Docs regarding rate limits, but it only mentions general guidance without specific TPS limits for this endpoint.
Is there a hard limit on POST requests for NLU intents during load testing? We are seeing this behavior consistently across three different runs. The environment is Genesys Cloud EU-West-1. We are using the latest JMeter 5.6.2. Any advice on how to structure the test to avoid hitting this wall without reducing concurrency significantly?