Ran into a weird issue today with the Workforce Management API endpoints returning 504 Gateway Timeout errors specifically during peak traffic windows in Asia/Singapore. This latency coincides exactly with intermittent SIP registration failures on three of our fifteen BYOC trunks.
The custom Architect flow handling outbound routing seems to hang when querying real-time trunk health metrics. The failover logic does not trigger until the timeout expires, causing significant call abandonment spikes.
Has anyone seen this correlation between trunk registration instability and WFM API responsiveness? Need to determine if this is a platform-side throttling issue or a carrier-specific quirk affecting our aggregation scripts.