could someone explain why our sip trunk registration is dropping right after we push the weekly schedule? we are using the genesys cloud api v2.140.0 to automate the wfm schedule publish on tuesdays at 10 am central time. normally the trunk stays healthy but since last week we see a spike in 503 service unavailable errors on the inbound leg. the error logs show [sip] registration timeout for endpoint trunk_01. it seems like the schedule publish job is somehow interfering with the telephony stack or maybe there is a resource contention issue. we have tried staggering the api calls but the issue persists. the agents are reporting dropped calls during the publish window which is causing major adherence issues. is there a known conflict between the wfm schedule optimization process and the sip trunk keep-alive mechanism? we need this fixed before the next payroll cycle. any insights on how to isolate the wfm api calls from the telephony layer would be appreciated.