⚠️ Error: The simulator stops or shows strange behavior

💡 Probable cause: One of the most common causes is that one of the branches of a Response Evaluator is empty or without a defined value.

This occurs, for example, when a condition based on buttons or options is created, but one of the branches is not completed with an action or next block.

🧩 Typical example:

You have a message with three buttons: "Yes", "No", "Maybe".

You only defined actions for "Yes" and "No".

The "Maybe" branch was left empty.

When simulating that flow, the route is cut off or an error is displayed because the simulator cannot continue.

✅ Suggested solution: Make sure to complete all branches of the evaluator before starting the simulation. If some option should not execute any action yet, you can add a "Comment" type block or a temporary action as a placeholder.

🔹 Check that all evaluators have defined values in each branch.🔹 If you duplicated a flow, validate that the buttons are still correctly linked to their evaluators.🔹 Use internal test campaigns such as "Test1" before activating real flows.🔹 Make sure that the required information fields are correctly configured.

The simulator is a great tool to validate the route, but it does not replace a real test. Whenever possible, do internal tests in a controlled environment with test users before publishing the flow in production.