Just noticed that our weekly schedule publish workflow is hitting a wall when agents attempt to finalize shift trades via the self-service portal. The system throws a 422 Unprocessable Entity on the POST /api/v2/wfm/schedules/{scheduleId}/shift-trades endpoint, specifically citing constraint_violation: overlapping_unavailable_time. This happens even when the proposed swap clearly respects the minimum rest period and does not overlap with any existing time-off requests in the UI. We are running Genesys Cloud version 2023-12-01 with the WEM module fully enabled in our Chicago BYOC environment. The error payload includes "code": "422", "message": "The shift trade violates one or more scheduling constraints.", but the details array is empty, offering zero insight into which specific rule is being triggered. I have verified the agent profiles, and both parties have the wfm:schedule:write permission. The issue seems isolated to trades involving part-time agents with complex availability windows defined in their profile. When I check the GET /api/v2/wfm/schedules/{scheduleId}/constraints endpoint, the configuration looks standard, with no custom rules that should block this specific pair. However, the adherence reporting still shows these agents as compliant, suggesting the conflict might be a calculation lag or a bug in the constraint engine’s evaluation of partial-day availabilities. Has anyone seen this behavior with part-time agent constraints? I need to know if there is a workaround to manually approve these trades or if we need to adjust the constraint granularity in the WEM settings. The current blockage is causing significant friction in our shift swap process, and agents are bypassing the portal to request changes via email, which defeats the purpose of the self-service feature. I suspect it might be related to how the API handles timezone conversions for the Chicago edge cluster, but I want to rule out a configuration error first before escalating to support.