Predictive Routing Campaign Error 400 with BYOC Trunk Metadata

Quick question about configuring Predictive Routing campaigns linked to our 15 BYOC trunks in APAC. When injecting custom carrier failover logic via Architect, the campaign deployment fails with HTTP 400 Bad Request. The error payload indicates a mismatch in the outbound_calling_station_id schema. Does the predictive engine require specific metadata tagging for BYOC endpoints, or is this a known limitation with cross-region trunk routing? Any insights appreciated.