POST /api/v2/schedules/publish failing with 409 Conflict on overlapping availability

Having some issues getting my configuration to work when attempting to publish the weekly schedule via the WFM API.

We are hitting a 409 Conflict error on the POST /api/v2/schedules/publish endpoint. The payload includes valid shift trades and time-off requests approved in the self-service portal, but the API rejects the batch due to an internal overlap validation that does not appear in the UI. The conflict seems to stem from agents having overlapping availability windows defined in the resource group versus the specific shift assignments. We are using the standard WFM API v2 endpoints and our environment is in the US-1 region. The error message is vague, returning only a generic conflict code without specifying which resource or time slot is causing the issue. We need to know if there is a specific validation rule for shift swaps that differs between the UI publish flow and the API endpoint.