Could someone explain why our Architect flow is failing to update the WFM schedule group attributes when triggered by a digital channel event? We are using the REST API client in Architect to push shift swap approvals back to the WFM schedule group. The flow executes without error, but the schedule group data remains unchanged. We are seeing a 204 No Content response from the API call, which suggests success, yet the agent preferences in the schedule group do not reflect the approved swap. This happens consistently for our Chicago-based team during the weekly publishing cycle.
The environment is Genesys Cloud US East, and we are using the latest Architect version. The payload matches the schema requirements for the schedule group update endpoint. We have verified that the API key has the necessary WFM permissions. Is there a known delay in propagating these updates from the Architect flow to the WFM module? Or could this be related to how digital channel events are processed in the background? We need this integration to work seamlessly for our shift swap workflow.