I’m completely stumped as to why the Predictive Routing API returns a 400 Bad Request when attempting to activate a campaign that relies on specific BYOC trunk constraints. The environment is Genesys Cloud (v2023.10) in the Singapore region. We are managing 15 BYOC trunks, and this specific campaign is designed to route only through our primary Singapore carrier trunk (Trunk ID: trk_sg_primary_01) to ensure compliance with local numbering regulations.
The error response indicates a validation failure on the routing_campaign object, specifically citing an issue with the outbound_flow_id or associated trunk_selection rules, yet the Architect flow is valid and the trunk is registered and active. I have verified that the OAuth token has full predictive_routing:campaign:write permissions.
Here is the payload I am sending to POST /api/v2/predictive/campaigns:
{
"name": "SG_Promo_Outbound",
"contact_list_id": "cl_sg_contacts_99",
"outbound_flow_id": "flow_sg_promo_v2",
"state": "ACTIVE",
"configuration": {
"call_rate": 10,
"max_calls_per_hour": 500,
"trunk_selection_rules": [
{
"trunk_id": "trk_sg_primary_01",
"priority": 1
}
]
}
}
The error message returned is: {"message": "Invalid trunk selection rule: Trunk does not support predictive routing capacity constraints."}. This is confusing because the trunk is fully configured for BYOC and handles high-volume inbound traffic without issue. Has anyone encountered similar validation errors when restricting predictive campaigns to specific BYOC trunks?