Why does the Architect API is rejecting our IVR flow updates with a validation error that doesn’t clearly specify the offending node? We are deploying a multi-tenant Premium App that programmatically updates IVR structures for several clients via the /api/v2/architect/flows endpoint. The request payload is a valid JSON representation of the flow, verified against the schema locally. However, upon POSTing the update, we receive a 400 Bad Request. The response body contains a generic message: “Validation failed for the flow.” No specific error codes or node IDs are included in the errors array. This makes debugging nearly impossible when dealing with complex flows containing nested sub-flows and data transforms. We have confirmed that the OAuth tokens have the necessary architect:flows:write permissions. The issue persists across different environments (us-east-1 and eu-west-1). We suspect this might be related to a recent change in the Architect validation logic or a limitation in how the API handles certain node types, such as the new AI-assisted routing nodes. Any insights into how to extract detailed validation errors or known issues with bulk flow updates would be appreciated. How can we obtain detailed validation error messages for failed IVR flow deployments via the Architect API?