This article discusses the most common types of errors that should be validated before publishing Eddie flows, as well as how to identify and fix them. Adopting these best practices helps ensure that the flow functions cohesively, all paths are covered, and the end-user experience remains consistent.
Automatic Validation in the Editor
Eddie 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 the flow from being published, but it is recommended that all issues be reviewed and resolved before the flow goes into production.
Known Errors
Missing ClaudIA block in branches
Each branch of the flow must have at least one ClaudIA block before the end of the path. ClaudIA needs this information to identify that the flow has ended and to take the necessary actions (continue support, resolve N1, escalate to N2, etc.).
Missing text associated with 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 positioned between them.
Incomplete Conditions
Alerts when conditional blocks (IF, ELSE) are not properly filled out. It is important that all outputs from the conditional 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 been published yet. This warning can be ignored during flow creation but must be resolved at the time of publication.
Missing text between input blocks
Occurs when sequences of text input blocks are connected directly without a message between them. To prevent errors in ClaudIA integration, it is necessary to always send a message before any information collection.
Conclusion
Ensuring that all Eddie flows are validated before publishing is essential to provide a smooth user experience, reduce operational errors, and maintain the integrity of Claudia's logic. With the validations and best practices outlined here, your team can build more robust, predictable, and easier-to-maintain flows.