The Architect flow is throwing a ‘No Available Agents’ error code 404 when attempting to route calls to the ‘WFM_Scheduled_Group’ queue, despite the WFM dashboard showing 15 agents logged in and available. This issue manifests specifically during the Tuesday morning peak shift (08:00 AM - 10:00 AM CT) in Genesys Cloud version 2024-3.0. The flow logic uses a ‘Set User Attributes’ block to pull the agent’s scheduled shift status via the WFM API, but the response payload seems to lag behind the actual schedule publish. We noticed that after the weekly schedule publish completes on Monday night, the agent availability flags in Architect do not sync correctly until a manual cache refresh is triggered. The specific error log shows: ‘Queue routing failed: Agent state mismatch between WFM and Architect routing engine.’ We have verified that the agents are indeed logged in, their skills match the queue requirements, and their WFM schedule shows them as ‘Available’ for the current time slot. However, the Architect flow treats them as ‘Offline’ or ‘Busy’ based on an outdated state. We are using the standard WFM integration webhook to push schedule changes to the user attributes, but the latency appears to be causing a race condition. The webhook endpoint is https://api.us-gov.genesis.com/v2/wfm/schedules/publish, and it returns a 200 OK, but the downstream Architect routing does not reflect the new availability immediately. We need to know if there is a way to force an immediate synchronization between the WFM schedule publish and the Architect routing engine, or if we need to add a delay block in the flow to wait for the state update. This is causing a significant drop in service level during the first two hours of the business day. Any insights on how to debug this state mismatch or optimize the webhook processing time would be greatly appreciated.