Stumbled on a weird bug today with the WFM schedule adherence reporting API. When pulling data for last week’s Chicago shift via GET /api/v2/wfm/schedules/adherence, the endpoint returns a 500 Internal Server Error specifically for agents who participated in shift swaps. Direct schedule assignments return data correctly with 200 OK responses. The error payload is empty, providing no trace ID or specific field violation. This happens consistently during our weekly publish window on Tuesdays between 09:00 and 11:00 CST. Agents who swapped shifts show zero adherence data in the dashboard UI as well, suggesting a backend calculation failure rather than just an API glitch. We are using the Genesys Cloud REST API v2. Has anyone seen issues with the adherence engine failing to resolve swapped shift metadata correctly? Need to resolve this before Monday’s forecast review.