Struggling to figure out why our Predictive Routing campaigns are stalling immediately after the weekly schedule publication window closes. We operate in America/Chicago and push final schedules every Friday at 4 PM Central. The WFM integration confirms that the schedule status is ‘Published’ and agent capacities are updated in the WFM dashboard without issue. However, within minutes of the publish completing, our primary outbound campaign (ID: CAMP-8821) drops its active agent count to zero and the call distribution rate plummets from 45 calls/minute to near zero. The Architect flow logs show no errors in the IVR routing logic, and the Predictive Routing console displays ‘Ready’ status for the campaign. I have verified that the ‘Agent Availability’ data source in the flow is correctly pointing to the latest WFM schedule version (v.24.1.0). I also checked the /api/v2/wfm/schedules/adherence endpoint for a sample of agents who have shifts starting Saturday morning, and it returns valid availability windows. Despite this, the routing engine seems to treat these agents as unavailable or unstaffed. I have attempted to restart the campaign and clear the local cache on the routing servers, but the issue persists. The logs in the Genesys Cloud admin console do not show any explicit ‘Staffing Mismatch’ or ‘Capacity Error’ codes, which makes debugging difficult. It appears there is a latency or sync issue between the WFM schedule publish event and the Predictive Routing staffing calculation engine. The problem resolves itself spontaneously after about 45 minutes, suggesting a background job or cache refresh is eventually correcting the data. Has anyone seen a delay in staffing data propagation from WFM to Predictive Routing specifically following a large-scale Friday publish? I need to ensure our Saturday morning ramp-up is not impacted by this lag.