Quick question about rate limiting on the Quality Management endpoints. Running JMeter 5.6 to simulate concurrent quality evaluation submissions in US1. The goal is to verify how the system handles bulk evaluation creation during peak WFM scheduling windows. Using the /api/v2/quality/evaluations endpoint with POST requests. Each request includes a standard evaluation form payload with 15 scoring points. Simulating 30 concurrent evaluators submitting one evaluation every 10 seconds. After 5 minutes of steady state, hitting 429 Too Many Requests errors on roughly 40% of the requests. The error response includes a Retry-After header set to 3 seconds. This is causing significant backlog in the test results. The documentation mentions general API rate limits but does not specify exact thresholds for quality evaluation creation. Need to understand if this is a global limit or per-user limit. The environment is a standard Genesys Cloud tenant with no custom rate limit overrides configured. Load pattern is linear ramp-up to 30 concurrent users, then steady state for 10 minutes. CPU and memory usage on the JMeter server is nominal, so the bottleneck is clearly on the API side. Want to ensure the WFM team can schedule evaluations without hitting these limits during actual business hours. The current failure rate makes it difficult to validate the evaluation workflow under load. Any insights into the specific rate limit for this endpoint would be helpful. Also interested if there are recommended batching strategies or async patterns for bulk evaluation creation. Currently using synchronous POST requests with immediate response validation. Switching to async might help but need to confirm if the API supports it for this resource. The test script includes proper authentication token refresh logic, so token expiration is not the issue. Rate limiting appears to be the primary constraint. Looking for best practices to avoid 429 errors while maintaining high throughput for evaluation submissions. This is critical for capacity planning in our load testing framework. Need to model the correct arrival rate to prevent API throttling in production scenarios. Appreciate any guidance on configuring JMeter to respect the Retry-After header automatically. Currently implementing a custom listener to handle delays, but it adds complexity to the test plan. Seeking a cleaner approach if one exists.