Does anyone understand why the schedule adherence endpoint is rejecting perfectly valid shift swap data? We are running Genesys Cloud version 23.10 in the US-East region. Our weekly schedule publication process has been stable for months, but since the last patch, the /api/v2/wfm/schedule/adherence call starts failing for specific agent records. The error payload returns a 400 Bad Request with the message “Invalid time range for shift swap”.
We have verified the timestamps in the request body. The start and end times align perfectly with the approved shift swap window in the WFM UI. The agents involved are in the America/Chicago timezone, and the API request includes the correct X-Genesys-Application header. We are using the standard Java SDK v23.10.0.
It seems to happen only when the swap crosses a day boundary at midnight. Is there a known bug with date parsing in the adherence engine for cross-day swaps? We need to get the weekly report generated before our Monday meeting. Why is the API rejecting valid cross-day shift swaps with a 400 error?