No idea why this is happening, the bulk schedule publish fails with a 409 conflict when agent data masking is enabled.
We are running Genesys Cloud version 2023-12 with the latest WFM SDK. When we attempt to publish schedules for our Chicago-based agents (America/Chicago timezone), the API returns a 409 error specifically on the genesyscloud_security_data_masking resource. This only happens when the agents have opted into the self-service shift swap feature. The error message indicates a database replication lag issue, similar to what we saw in the APAC region last month, but we are on the US-East cluster. The payload includes standard adherence rules and time-off requests. I have verified that the agent profiles are correctly masked and that the schedule data does not contain any PII that should trigger a conflict. The issue seems to stem from the interaction between the WFM scheduling engine and the security masking layer during the bulk operation. We need to resolve this to meet our weekly publishing deadline. Has anyone encountered this specific interaction between WFM bulk operations and data masking policies? We are looking for a workaround or a configuration change that allows the publish to complete without triggering the 409 conflict. The current setup blocks our entire scheduling workflow.