The IVR Settings block is dropping outbound calls when the api integration pipeline pushes a modified DTMF sequence through the Architect SDK. The execution flow begins by constructing a POST request to /api/v2/architect/flows, which includes a TransferToQueue step bound to the Queue Configuration. The payload gets validated locally, yet the server returns a 422 Unprocessable Entity referencing invalid_transfer_parameters. This stalled the evening shift routing for three hours.
The routing logic attempts to map the external carrier data to the Routing Profile, but the schema validation rejects the destination_type field. We’ve verified the OAuth2 token scope covers architect:write, and the tenant ID matches the hybrid platform deployment. The error traces back to the TransferToQueue node expecting a string identifier, while the api integration layer supplies a UUID array. Schema cache probably hasn’t refreshed. The validation routine is doing jack all with that format.
- Architect version: 2023-11.291.0
- SDK: Java 10.0.15
- Queue Configuration: Standard IVR routing
- Payload size: 1.2KB
The response body shows {"code":"invalid_transfer_parameters","message":"destination_type mismatch"}. Adjusting the destination_type to queue didn’t resolve the schema lock. The next step involves checking the TransferToQueue block validation rules against the current api integration spec