Ran into a weird issue today with the WFM Schedule Data Action in Architect when attempting to pull live schedule data for our weekly publication workflow. The flow hangs indefinitely at the data action step, eventually timing out after 30 seconds, which disrupts the entire schedule publishing process. This happens consistently around 08:00 CST on Mondays, right when agent self-service updates are syncing.
We are using the standard GetSchedule data action with the scheduleId parameter passed from a previous HTTP request step. The API documentation suggests this should be a lightweight call, but the latency is unacceptable for our workflow. We have verified that the underlying schedule exists and is not in a locked state.
Has anyone else seen performance degradation with WFM data actions during peak scheduling hours? We are trying to determine if this is a platform limitation or a configuration issue on our end. We need a reliable way to fetch schedule data without blocking the flow, or an alternative endpoint that handles concurrent requests better. Any insights on optimizing this or a workaround would be greatly appreciated.