WFM schedule publish breaks Digital Messaging agent availability in Chicago

Could someone explain why Digital Messaging treats agents as unavailable immediately after a WFM schedule publish in Chicago?

Running Genesys Cloud v24.5.0.

Shift swaps approved via self-service show as active in WFM but the Digital queue drops them.

Error 409 Conflict appears in the API logs.