There are times when a project flow is removed / edited that then impacts a different flow that calls it. This error may then stop us from saving the primary flow or stops the flow from working when it is used in the assistant, which is not always immediately obvious.
Is there a way you can provide warnings / information within a project flow / conversation flow so that:
Any issues are easily identifiable when a flow is opened in the editor. This would be helpful for the caller and callee flow.
Ability to understand how project flows are connected and what dependencies exist, which would be really helpful to know before we edit or delete a project flow?
A flow with errors can be saved, allowing us to either come back to it later (e.g. an in-development flow) or go and update a different flow. At the moment, we either lose our changes or have to open new tabs within the browser.
