I’m curious as to why the /api/v2/wfm/schedules/adherence/report endpoint returns a 400 Bad Request when filtering by agents with active shift swaps?
We publish schedules every Friday at 10:00 AM CST. The standard adherence query works fine for agents with static shifts. However, when we include agents who submitted swap requests via the self-service portal, the API throws a validation error: Invalid filter criteria: agent_id must have a valid schedule assignment for the requested time range.
The swap is approved in the UI, and the schedule reflects the new shift times. Yet the API seems to still reference the original shift ID or fails to resolve the swapped agent’s assignment. We are using the latest WFM SDK version 2.4.1. Is this a known limitation with how the adherence engine handles swapped shift metadata? We need accurate adherence metrics for these agents before the weekly compliance review.
Any insights on resolving this or a workaround to fetch adherence data for swapped shifts would be appreciated.
Thanks for the help.