Just noticed that our updated IVR flow fails validation immediately after adding the new schedule lookup task.
The environment is Genesys Cloud v2023-12, and we are attempting to route calls based on the real-time availability of our WFM-published schedules for the America/Chicago timezone. The flow previously worked fine with static date ranges, but switching to dynamic schedule adherence checks triggers a validation error. The specific error message in the Architect console is: “Task ‘Schedule Lookup’ failed validation: Invalid input parameter ‘agent_group_id’. Expected string, got null.” We have verified that the variable mapping from the previous task is correct and contains a valid UUID. The schedule lookup task is configured to query the WFM API for available agents in the ‘Tier 1 Support’ group. Despite the group existing and having published shifts, the flow engine seems to reject the dynamic reference during the pre-publish validation phase. We are using the standard ‘Lookup Schedule Availability’ task block. Has anyone successfully implemented real-time WFM schedule integration within an Architect flow without hitting this specific null parameter error? We need this live before the weekly schedule publication on Friday.