Outbound Dialer Campaign Stuck in Error State After WFM Publish

409 Conflict: Schedule Conflict Detected

What is the correct way to resolve outbound dialer campaign errors triggered by WFM schedule updates? We are running Genesys Cloud v24.5.0 in the Chicago environment. The campaign fails to start when the WFM API updates agent availability mid-predictive run. The error blocks the entire queue, forcing a manual reset. Is there a configuration to ignore transient WFM sync conflicts during active campaigns?