Quick question about BYOC WFM Schedule Group API conflicts

Quick question about handling schedule group conflicts when deploying via BYOC.

We are using the WFM Schedule Group API to automate weekly publishing for our Chicago team. Everything works fine until we hit a shift swap request that overlaps with a previously published block. The API returns a 409 Conflict error with the message “Schedule group version mismatch.”

Is there a specific header or parameter we need to include to force an override during off-hours? We want to avoid manual intervention but also don’t want to accidentally overwrite active agent shifts.

Any insights on best practices for this scenario would be greatly appreciated. We are currently running the latest stable SDK version and have verified the timezone settings are correct for CDT.

The documentation actually says you need to include the If-Match header with the current ETag value from the initial GET request.

This ensures the system validates the version before applying the patch.

Without it, the 409 Conflict is the expected behavior to prevent data loss.