Outbound Campaign Pauses Unexpectedly After WFM Shift Boundary

Can anyone clarify why our outbound campaign drops to zero progress exactly at 17:00 CST, matching our shift end time? We are on Genesys Cloud v24.5.0 in the Chicago environment. The dialer seems to respect the WFM schedule publish too aggressively, ignoring the ‘ignore_schedule’ flag in the campaign config below.

campaign:
 name: "Q4 Follow-up"
 dialing_mode: predictive
 schedule_override: false
 wfm_integration: enabled

Is there a known conflict with the WFM API sync?