Having some config trouble here. we are deploying an updated ivr flow via our appfoundry integration but hitting a 400 bad request on the post /api/v2/architect/flows endpoint. the error response indicates a validation failure on the initial ivr node specifically regarding the max duration setting.
we are using the platform api v2 and have verified the json payload matches the schema requirements for the ivr:write scope. the issue seems isolated to flows that include a nested sub-flow reference with a custom timeout value exceeding 30 seconds. interestingly, manual updates through the architect ui succeed without issue, suggesting the api validation logic might be stricter or slightly out of sync with the ui constraints.
our integration handles multi-org deployments and this failure is causing significant delays in our client provisioning pipeline. we have checked the rate limits and headers are correct. has anyone else encountered this specific validation mismatch between the ui and api for ivr node configurations? any insights on the exact constraint being violated would be appreciated. we are running the latest stable version of our sdk wrapper.