BYOC Trunk Registration Flapping After Weekly Schedule Publish in Chicago

My current config is completely failing… we are seeing a critical registration flap on our BYOC trunks immediately following the Friday 4:00 PM CT schedule publish. The SIP registration state toggles between REGISTERED and UNREGISTERED every 15 seconds for about 10 minutes. This coincides exactly with the WFM capacity recalculation job firing on the backend.

We are running Genesys Cloud release 23.2. The issue only affects our primary Chicago datacenter trunks, not the secondary failover. The SIP logs show a 403 Forbidden response from the Genesys Cloud SIP proxy right after the schedule is locked, which forces the SBC to re-register.

Is there a known dependency between the WFM publishing API (/api/v2/wfm/schedules) and the BYOC trunk registration service? I have checked the trunk profile settings, and the registration_timeout is set to the default 60 seconds. I have also verified that no firewall rules are changing during this window.

This is disrupting our inbound call routing because agents are showing as available, but the trunk cannot accept new calls during the flap. Has anyone encountered this specific timing correlation? We need a workaround to stabilize the trunks during our weekly publish window.

Have you tried checking if the WFM capacity updates are triggering unnecessary BYOC trunk re-registrations? In Zendesk, bulk updates often caused similar API churn. Try disabling the automatic trunk registration refresh during the WFM job window in Genesys Cloud. This usually stops the flapping by decoupling the schedule publish from the SIP state machine.