What is the standard approach to sync schedule adherence events in a Bring Your Own Cloud deployment when the local WFM server is in America/Chicago?
The /api/v2/wfm/schedules/adherence endpoint returns stale data for agents in the night_shift group. There is a 15-minute delay between status changes in the local scheduler and the Cloud UI. This breaks our real-time adherence monitoring workflows.