Just noticed that the Workforce Management schedule endpoints are returning 429 Too Many Requests errors when JMeter 5.6.2 hits just 10 concurrent threads. The specific endpoint causing issues is PUT /api/v2/wfm/schedules/segments/{segmentId}. We are testing from Asia/Singapore against a Genesys Cloud BYOC Edge environment. The latency is normal, around 200ms, but the throttling kicks in almost immediately after the ramp-up phase. This seems unusually aggressive for such low concurrency, especially compared to other API modules we tested previously. We have verified that the authentication tokens are valid and cached correctly. The JMeter thread group is configured with a 5-second ramp-up and a 1-minute loop duration. Is there a specific rate limit for WFM schedule operations that is lower than the general platform API limits? We need to understand if this is expected behavior or if there is a configuration issue on our side. Any insights into the throttling thresholds for WFM APIs would be appreciated. We are trying to establish baseline performance metrics for our load testing strategy.