POST /api/v2/architect/flows/ivr/{flowId}/settings returns a 500 Internal Server Error with the message “Invalid flow configuration” when attempting to update the defaultLanguage property through our AppFoundry integration. The request payload is minimal:
{
"defaultLanguage": "en-US"
}
This occurs specifically when the flow is currently active in a production environment (EU1 region). The same request succeeds without issue on staging instances where the flow status is inactive. We have verified that the multi-tenant OAuth token possesses the architect:flow:write scope and the associated user has the Architect:Edit permission set.
The error response lacks a detailed error code, making it difficult to pinpoint the exact validation failure. Is there a known limitation regarding runtime updates to IVR default language settings via the API, or is this a transient issue with the EU1 edge nodes? We are observing this behavior consistently across three different partner tenant accounts.
Has anyone encountered similar blocking behavior when modifying live flow configurations programmatically?