POST /v2/analytics/scripting/executions returns HTTP 500 with {“message”: “Trunk metadata injection failed for carrier SG-BYOC-04”}. This occurs exclusively when routing calls through our secondary Singapore carrier during off-peak hours.
The primary trunk works fine, and SIP logs show successful registration. The error persists across SDK v2.14 builds. Is there a known conflict between the new scripting engine and specific BYOC failover states?