SIP Trunk Failover Triggered by WFM Publish Overhead

Can anyone clarify why our primary SIP trunk registration drops intermittently during the weekly WFM schedule publish in Genesys Cloud 2024-2.0? The trunk_status API returns REGISTRATION_FAILED with code 408 right as the wfm:schedule:publish webhook fires. We see this spike in America/Chicago timezone around 08:00 AM CST. Is the publish job creating enough background load to cause SIP keep-alive timeouts?