This article highlights the most common error types that should be validated before publishing Controlled Flows, as well as how to identify and fix them. Adopting these best practices helps ensure the flow functions cohesively, all paths are covered, and the end-user experience remains consistent.
Automatic Validation in the Editor
Controlled Flow validation is performed automatically after each change made in the editor, providing real-time feedback on inconsistencies and points of attention. The validation does not prevent flow publication, but it is recommended that all issues be reviewed and resolved before deploying the flow to production.
Known Errors
ClaudIA Block Missing in Branches
Each branch of the flow must have at least one ClaudIA block before the path ends. ClaudIA needs this information to identify when the flow has ended and to take necessary actions (continue support, resolve N1, escalate to N2, etc.).
Text Missing Next to ClaudIA Block
The ClaudIA block exists but has no associated text. The text block can be positioned before or after the ClaudIA block, provided there is no Input block placed between them.
Incomplete Conditions
Indicates when conditional blocks (IF, ELSE) are not properly filled. It is important that all outputs of the condition are connected to some block, so the flow can proceed without errors.
Broken Links
Indicates that a link block points to a flow that no longer exists or has not yet been published. This warning can be ignored during flow construction, but it is crucial to resolve it at the time of publishing.
Missing Text Between Input Blocks
Occurs when there are sequences of connected text input blocks without any message text between them. To prevent errors in integration with ClaudIA, a message must always be sent before any information collection.
Conclusion
Ensuring that all Controlled Flows are validated before publication is essential to guarantee a smooth user experience, reduce operational errors, and maintain the integrity of Claudia's logic. With the validations and best practices described here, your team can build more robust, predictable, and maintainable flows.