Having some config trouble here. I am trying to automate the weekly schedule adherence report generation using the Genesys Cloud API. The goal is to pull adherence data for the Chicago timezone team immediately after the weekly publish completes.
The POST request to /api/v2/wfm/schedule/adherence/bulk returns a 400 Bad Request. The error payload indicates a validation failure on the timeOffReason field, specifically stating that the reason code ‘PTO’ is invalid for the given date range. This is confusing because ‘PTO’ is clearly defined in our time-off policies and agents use it successfully in the self-service portal.
“The time off reason must be valid for the specified date range and agent’s policy group. Ensure the reason code matches the configured policy.”
I have verified the policy group assignments via the admin console, and the reason codes appear correct. The issue seems isolated to the API call, as manual adherence checks in the UI show no errors. Is there a specific format required for the reason code in the bulk update body, or is this a known sync issue between the policy engine and the adherence calculation service? Any insights would be appreciated.