The schedule publish job is failing with a 409 Conflict error during the weekly Tuesday run in our US-East-1 environment. The specific payload rejection occurs when processing approved shift swaps for agents in the Central timezone.
We are using the /api/v2/wfm/scheduling/schedules endpoint via our custom orchestration script. The error log indicates: "message": "Schedule conflict detected for agent ID 12345 during swap window." This is strange because the swap was explicitly approved by the supervisor in the WFM UI three days ago, and the availability rules clearly permit this trade.
Our WFM version is 2024.3.0. We have verified that no other overlapping schedules exist for these agents. The issue seems isolated to swap approvals that cross the midnight boundary in CST. When we manually publish without the swap, the job succeeds. Is there a known bug with the shift trade validation logic in this release, or are we missing a configuration flag in the schedule definition JSON that forces a hard check on swap boundaries?