WFM Bulk Import API 429 Errors During JMeter Load Test on US1

Stuck on a rate limiting issue with the Workforce Management bulk import endpoints. The environment is Genesys Cloud US1. We are using JMeter 5.6 to validate capacity for schedule imports.

The specific endpoint is /api/v2/wfm/schedule/import. We are pushing 100 concurrent threads. Each thread sends a 50KB JSON payload representing agent schedules. The payload structure matches the schema exactly. No validation errors on the client side.

After about 10 seconds, the server starts returning HTTP 429 Too Many Requests. This happens even though we are well below the documented general API limits. The error response body contains a Retry-After header set to 5 seconds.

We have tried adding a constant timer in JMeter. We set it to 2000ms per thread. The 429 errors still occur. We reduced the concurrency to 50 threads. The errors disappeared. But we need to support higher throughput for our peak hiring seasons.

The error logs in Genesys Cloud do not show specific WFM rate limit details. They just show standard API gateway throttling. We are looking for the specific rate limit for this endpoint. Is it per tenant or per API key? We are using a service account for the load test.

We also checked the WebSocket connections. They seem stable. The issue is purely with the REST API calls. The JMeter config uses HTTP Request samplers with proper headers. We include the Authorization Bearer token. The token is refreshed automatically.

Has anyone tested the WFM import endpoints under load? We want to know the safe concurrency level. We are trying to model the system behavior for capacity planning. The current behavior suggests a hidden limit.

Any insights on how to tune JMeter for this endpoint would be helpful. We are open to using async requests if that helps. But we prefer to understand the synchronous limit first.

Please share your experience with WFM API rate limits. We are eager to optimize our test setup. Thank you for any guidance.