I’ve spent hours trying to figure out why the adherence engine is flagging agents for ‘Unscheduled Activity’ immediately after a shift swap is approved via the WFM API. We are using the Chicago cluster and publishing weekly. The swap logic seems correct, but the post-swap interval shows a gap in coverage despite the new agent being logged in. The error code returned is 409 Conflict on the adherence endpoint. How do we ensure the adherence calculation updates synchronously with the swap approval?