WFM Schedule Publish API 503 during High Concurrency JMeter Test

Quick question about the WFM schedule publish endpoint behavior under load. We are hitting a 503 Service Unavailable error when pushing weekly schedules via the API.

The environment is Genesys Cloud, version 2023.10. Our timezone is America/Chicago, which affects the shift start times in the payload.

We are using a batch size of 50 agents per request. The error occurs specifically when concurrent requests exceed 10. Rate limiting seems to be the culprit here.

Has anyone found a workaround for this? We need to automate the weekly publish process without manual intervention or delays.