The audit trail shows a successful PATCH to /api/v2/wfm/schedules but the compliance export flags a missing approval signature.
Our Chicago team relies on this weekly data for union reporting. The schedule publishes fine in the UI, and agent self-service shows the swap as active. Yet the downstream compliance check fails because the specific approval timestamp isn’t logging in the expected format. We are using the standard WFM API integration. Is there a known lag or formatting issue with how shift trade approvals are recorded in the audit logs versus the schedule state? We need to ensure our records match exactly for the upcoming audit cycle.