Why does this setting in Predictive Routing configuration cause call distribution skew when primary BYOC trunks experience intermittent SIP 408 timeouts? We operate 15 trunks across APAC regions, specifically Singapore and Tokyo endpoints. During scheduled maintenance windows, we observe a ~300ms delay in failover to secondary carriers. This latency appears to trigger the predictive engine to mark agents as ‘unavailable’ prematurely, resulting in a 15% drop in service level for high-priority queues. The Architect flow handles the SIP registration drop gracefully, but the WFM integration reports schedule adherence violations due to the routing logic interpreting the failover gap as agent idle time. We are using Genesys Cloud version 2023.4 with the latest predictive routing algorithms enabled. The issue persists even when we adjust the ‘ring time’ and ‘connect time’ thresholds in the routing strategy. Is there a specific configuration parameter to decouple trunk failover latency from agent availability status in predictive routing? We need to maintain SLA compliance without penalizing agents for carrier-side network instability. The current setup forces a hard reset of the routing session, which disrupts long-running predictive campaigns. Any insights on stabilizing the routing logic during these specific network events would be appreciated.