I’m trying to figure out why the audit trail in Genesys Cloud is not capturing the specific shift_swap events when they are executed via the WFM API during our weekly publish window. Our environment is running Genesys Cloud 2024.1, and we have a strict compliance requirement to log all schedule modifications for the next quarterly SOC 2 audit. The standard POST /api/v2/wfm/schedule/publish call succeeds with a 200 OK, but when querying the audit log endpoint /api/v2/analytics/audit for the corresponding time range, the event_type for shift swaps is missing or shows as null for agents who used the self-service portal. We are using the Genesys Cloud SDK v2.0.1 in Python for our integration. The schedule adherence reports show the swaps are valid and applied, so the data exists in the WFM module, but the compliance layer cannot verify the actor or timestamp. Has anyone configured custom audit logging for WFM shift trades before? We need to ensure every swap is traceable to the agent’s user ID without manually scraping the WFM UI logs, which is not scalable for our 500+ agent floor. Any insights on why the audit stream might be filtering these specific WFM events would be huge.