Quick question about the Architect flow bulk import API behavior when dealing with complex BYOC trunk selection logic. We are migrating 15 BYOC trunks across APAC regions into a unified outbound campaign structure. The individual flow updates via the UI complete successfully, but when attempting to bulk import the JSON definitions via the Platform API, the endpoint returns a 422 Unprocessable Entity error. The error message is vague, citing a validation failure on the ‘Select Trunk’ action node without specifying which parameter is invalid. We have verified the JSON against the schema and confirmed all trunk IDs exist and are active in the Singapore and Tokyo edges. The failover logic uses a standard priority list, which works in the sandbox environment. Is there a known limitation with bulk imports when referencing multi-region trunk configurations or specific SIP credential bindings? We are using the latest Python SDK and have checked the ETag versions. Need to know if this is a schema validation bug or a missing dependency in the bulk payload structure.