Simulation status, decisions, and cancel
Logic Builder simulation is more interactive than a simple “press run and wait” tool.
Once a run begins, the workspace starts guiding you through the active path.
What you should expect after Run
When you click Run on a valid flow:
- the simulation status should change
- the execution trace should begin filling in
- the canvas enters a temporary locked state
- Run changes into Cancel
If none of those changes happen, treat that as a signal to inspect validation or flow structure.
What the Simulation panel tells you
The Simulation tab is where you read the main run feedback:
- Status
- Execution trace
- Final outcome
- validation issues if the flow is not ready
Do not rely only on the canvas animation. The side panel is the main place where the tool explains the run back to you.
What happens on active nodes
During simulation, the active nodes can display an overlay-style narration.
That overlay helps you understand:
- which node is currently active
- what the system is doing there
- when a decision needs your input
If you want the text to reveal faster, the tool supports skipping the reveal on the active node.
How decisions work during a run
When the flow reaches a Decision node:
- the simulation pauses for that node
- the active decision is surfaced directly on the node
- you choose Yes or No
- the run continues on that branch
This is important: the choice is not just abstract logic in the side panel. It becomes a live interaction inside the running flow.
Why the canvas becomes locked
While the simulation is active, editing is intentionally locked.
That protects the run from changing shape halfway through.
During that period, do not expect to:
- drag nodes around
- reconnect branches
- delete parts of the flow
If editing suddenly stops working during a run, the tool is doing its job.
When to use Cancel
Use Cancel when:
- you launched the wrong flow
- the run is no longer the one you want to inspect
- you already learned what you needed from the partial trace
Cancel is cleaner than waiting through the rest of an irrelevant run.
Good learner testing pattern
For meaningful practice:
- run a small valid flow
- watch the status change
- read the first execution trace entries
- handle a Yes/No decision when it appears
- read the final outcome
- cancel early only when the current run stopped being useful
That sequence teaches both structure and behavior together.