No idea why this is happening, the POST /api/v2/wfm/schedules/publish endpoint is returning a 409 Conflict error specifically for agents who have approved shift swaps in the current scheduling period. We are operating out of America/Chicago, and our weekly schedule publication job runs every Sunday at 02:00 CT to handle the timezone transition cleanly. The job processes approximately 400 agents, and while 95% publish successfully, the remaining 5% consistently fail with the error code SCHEDULE_CONFLICT_SWAP_OVERRIDE. The request payload includes forcePublish: true and includeAdherence: true, which should theoretically resolve minor conflicts. However, the error response body explicitly states: "message": "Cannot publish schedule due to unresolved swap conflict for agent ID 12345. Swap request ID SW-998877 has overlapping coverage requirements.". I have verified that the swap requests are fully approved by both the swapping agents and the supervisor, and the swapStatus in the response from GET /api/v2/wfm/schedule/swaps is APPROVED. The agents involved are not on PTO, and their availability windows are correctly defined in the agentAvailability object. I suspect there is a race condition or a validation logic issue where the bulk publish engine does not recognize the swap as finalizing the coverage gap before attempting to validate adherence rules. We are using the Genesys Cloud REST API v2 with a service account that has wfm:schedule:write and wfm:schedule:publish permissions. Has anyone encountered this specific SCHEDULE_CONFLICT_SWAP_OVERRIDE behavior when using forcePublish? We need a reliable way to automate this weekly process without manual intervention for these edge cases. The current workaround of manually publishing individual schedules is not scalable for our volume. Any insights into the validation sequence or a flag to explicitly acknowledge swap coverage during bulk publish would be greatly appreciated.