My configuration keeps failing after the Tuesday schedule push. Agents with shift swaps in Chicago are stuck in the digital queue despite showing ‘available’ in WFM. The /api/v2/wfm/schedules endpoint confirms the swap, but the messaging flow logic fails to route because the availability status lags by 30 seconds. Is this a known sync delay between WFM and the digital orchestration engine? Need a fix before the next publish window opens.