Quick question about the integration between WFM shift swaps and our custom Data Action for updating external HR systems. We are running into a consistent failure when the Data Action triggers upon shift_swap_approved events in the Chicago cluster. The flow works perfectly for standard schedule publishing, but as soon as a swap involves a cross-skill agent moving into a different availability window, the HTTP request to our endpoint fails with a timeout.
The Data Action is configured to use the agent_schedule object, but it seems the payload is malformed when the swap changes the agent’s primary skill group for that interval. We are using the latest version of the Architect and the standard WFM integration templates.
Here is the error returned in the Data Action logs:
Error: 504 Gateway Timeout. Request body validation failed. Field ‘availability_start’ does not match expected ISO 8601 format. Payload: {“agent_id”: “12345”, “availability_start”: null, “skill_group”: “support_tier2”}
The availability_start coming back as null is strange because the shift swap clearly defines a start time in the WFM UI. Is there a known issue with how the WFM API serializes shift swap intervals when they overlap with existing published schedules? We need this to sync correctly before the weekly schedule freeze.