Looking for advice on WFM scheduling conflicts.
The /v2/wfm/scheduling API returns a 500 error.
This happens during BYOC trunk failover in Asia/Singapore.
SIP registration drops on primary trunks.
WFM agents show as offline incorrectly.
Analytics reports miss wrap-up codes.
Is this a known sync issue?