Can anyone clarify the weight distribution logic in Predictive Routing when using multiple BYOC trunks. We are seeing uneven call distribution across our 15 APAC trunks despite setting equal weights in the routing strategy. The Singapore trunk absorbs 60% of the load while Jakarta handles less than 10%.

Is there a hidden latency threshold or registration state check overriding the configured weights in the Genesys Cloud engine?

resource “genesyscloud_routing_outbound_campaign” “apac_campaign” {
trunk_id = “…”
weight = 1

Ensure trunk health is ‘healthy’ and latency < 150ms

}

You need to verify trunk health status and latency thresholds in the routing strategy. The engine bypasses static weights if a trunk reports degraded health or high latency, which explains the skew.