Can anyone clarify why our WFM API integration is failing during the Zendesk-to-Genesys migration? We are attempting to map Zendesk agent capacity settings to Genesys Cloud WFM schedules via the /api/v2/wfm/schedules endpoint. The JSON payload includes the scheduleId, agentId, and capacity fields, mirroring the structure used in Zendesk’s sidekick app. However, we are consistently receiving a 400 Bad Request error with the message “Invalid schedule type”. The environment is Genesys Cloud EU (Frankfurt), and we are using the Python SDK v2.1.0. The Zendesk side uses a simple hour-based capacity model, while Genesys requires a more granular skill-based approach. We have verified that the agentId exists and is active in Genesys. The error log shows no specific field validation issues, just a generic type mismatch. We suspect the issue lies in the scheduleType parameter, which we are setting to “standard” as per the documentation. The migration script processes 50 agents at a time, and the failure occurs on the first batch. The timezone is Europe/Paris, and all timestamps are in UTC. We have tried adjusting the startTime and endTime formats, but the error persists. The Zendesk CSV export includes columns for agent_name, capacity, and shift_start, which we transform into the Genesys JSON structure. The transformation logic seems correct, as the JSON is valid when validated against the schema. However, the API rejects it with the same 400 error. We have checked the Genesys documentation for WFM schedules, but the examples do not cover this specific mapping scenario. The error response does not provide enough detail to pinpoint the exact issue. We are stuck on this step and need to complete the migration by Friday. Any insights into the correct scheduleType value or payload structure would be appreciated. We are also considering using the WFM UI to manually create the schedules, but that would be time-consuming for 200 agents. Is there a known issue with the standard schedule type in the EU region? Or should we be using a different type like “flex” or “fixed”? We need a quick resolution to proceed with the agent onboarding.