Trying to understand the race condition between WFM schedule publishing and Architect call routing logic.
Background
Environment: Genesys Cloud US-PROD (Chicago)
Role: WFM Coordinator publishing weekly schedules.
Issue
When a schedule is published that immediately changes an agent group’s status from ‘Offline’ to ‘Available’, Architect flows routing to that group via the ‘Queue’ action occasionally drop calls with a ‘No agents available’ error, despite the schedule being active. This happens within the first 60 seconds post-publish.
Troubleshooting
- Verified the schedule publish API returns 200 OK.
- Checked Architect flow logs; the routing decision happens before the agent state syncs.
- Is there a known latency or a specific Architect block to wait for WFM state consistency before queuing?