Does anyone know why approved shift swaps remain in a pending state immediately after a successful schedule publish in our US-East-1 environment? The /api/v2/wfm/schedules/publish endpoint returns a 200 OK, yet the agent self-service portal still displays the original shifts for the Chicago morning team.
- Verified the swap requests have ‘approved’ status via the WFM admin dashboard prior to the publish run.
- Confirmed no overlapping skill group assignments are causing a validation conflict in the Architect flow.