Data Action fails on WFM Schedule Publish for bulk shift swaps in America/Chicago

Stuck on a problem and need help troubleshooting a Data Action failure during our weekly schedule publish process. We are trying to automate the validation and execution of agent shift swaps via an Architect flow that triggers a custom Data Action. The goal is to ensure that when agents swap shifts in the WFM self-service portal, the downstream routing configuration updates immediately without manual intervention. However, the flow is consistently failing at the Data Action node with a generic INTERNAL_ERROR status, and the debug logs show a 500 Internal Server Error when the action attempts to call the /api/v2/wfm/scheduling/schedules endpoint.

Here is the sequence of events leading to the failure:

  1. An agent initiates a shift swap in the WFM Agent Desktop for the upcoming week in the America/Chicago timezone.
  2. The Architect flow detects the change via a webhook and retrieves the swap details using the wfmScheduling lookup.
  3. The flow passes the new schedule data to a custom Data Action named ValidateAndPublishSwap.
  4. The Data Action constructs a JSON payload matching the Schedule schema and sends a POST request to the publish endpoint.
  5. The request fails with a 500 error, and the schedule remains in a PENDING state, causing adherence reporting discrepancies.

We have verified that the service account has the wfm:schedule:manage permission, and manual API calls using Postman with the same payload succeed without issue. The error seems specific to the Data Action execution context. Is there a known limitation with bulk updates or specific header requirements when invoking WFM scheduling endpoints from within an Architect Data Action? We are currently on the 2024-02 Release. Any insights into why the context might be rejecting valid schedule objects would be appreciated.