Anyone know why the PATCH /api/v2/wfm/schedules/{scheduleId} endpoint is consistently returning a 409 Conflict error when attempting to finalize a batch of agent shift swaps during our weekly schedule publication in the America/Chicago timezone? We are using the Genesys Cloud 2024.5 platform and have verified that all proposed swaps comply with the configured min_hours_between_shifts and max_daily_hours business rules. The agents involved have sufficient available_time_off coverage, and the swap requests were approved via the self-service portal without flagging any initial conflicts. However, when the scheduling coordinator triggers the final publication step, the API rejects the changes with the message ScheduleConflict: Overlapping intervals detected for agent ID {agentId}. This is particularly frustrating because the overlapping intervals only appear to exist when comparing the swap against the previous week’s schedule, not the current draft. We have checked the wfm:schedule:view and wfm:schedule:edit permissions, which are correctly assigned to the coordinator role. The issue seems to stem from how the system calculates adherence to agent_preferences for break times when a swap crosses a midnight boundary in the America/Chicago timezone. Specifically, if Agent A swaps a shift ending at 23:59 with Agent B whose shift starts at 00:01, the system incorrectly flags a violation of the mandatory_rest_period despite the gap being exactly 2 minutes, which should be permissible under our current rest_period_config. We have tried adjusting the publication_window and disabling the auto_resolve_conflicts flag, but the 409 error persists. Has anyone encountered this specific edge case with midnight-crossing swaps in the latest release? Any insights into whether this is a known bug in the 2024.5 WFM module or a misconfiguration in our schedule_settings would be greatly appreciated. We need to resolve this before the Friday publication deadline to avoid manual overrides for over 50 agents.