Could someone explain the correct handling of outbound routing failures when the primary BYOC trunk drops SIP registration? We are managing 15 trunks across APAC regions, and during scheduled carrier maintenance, the Architect flow attempts to route calls to the secondary trunk. The issue is that the conversation:updated webhook fires a 502 Bad Gateway error before the failover logic completes.
502 Bad Gateway on outbound_call_initiated
The flow uses a ‘Play and Get DTMF’ block followed by an ‘Outbound Call’ block. When the primary trunk (SIP URI: sip:[email protected]) is down, the system hangs for 45 seconds before throwing the error. The analytics report shows a spike in ‘System Errors’ but no corresponding ‘Agent Not Available’ metrics. We suspect the webhook payload structure for the failed attempt includes null values for the routing_queue_id, causing the downstream ServiceNow integration to reject the update. Has anyone configured conditional logic to suppress the webhook if the trunk status is ‘Unregistered’? We need to prevent these false errors from skewing our SLA calculations.