Why is this setting causing a 400 Bad Request when pulling schedule adherence data via the Analytics Reporting API? We are running Genesys Cloud v24.5.0 in our Chicago environment and hitting a wall during the weekly schedule audit. The payload includes the standard adherence report parameters, but adding the shift_swap_history flag triggers the error immediately.
The API endpoint is GET /api/v2/analytics/reporting/schedules/adherence. The response body returns a clear validation error: “Invalid filter parameter: shift_swap_history is not supported for adherence reports.” This is confusing because the documentation for v24.5.0 explicitly lists this parameter under advanced filtering options for workforce management metrics.
Our team relies on this data to verify that agent self-service shift trades are correctly reflected in the final adherence scores. Without this flag, we have to manually cross-reference the shift swap logs, which defeats the purpose of the automated reporting pipeline. The issue persists across all test accounts and production users in the Chicago region.
Has anyone successfully used this parameter in v24.5.0? Are we missing a prerequisite configuration in the WFM settings, or is this a known bug in the current release? We need a workaround to automate this reconciliation process before our next weekly publish window opens.