Quick question about WFM Schedule Adherence API discrepancies

Quick question about requesting a historical adherence report. When filtering for agents with active shift swaps in our America/Chicago weekly publish, the report returns a 400 Bad Request. The schedule data looks correct in the UI, but the API fails to parse the swapped intervals. Is there a specific parameter format required for swapped shifts, or is this a known bug in the current release?