Debugging

Step debugging

Step debugging is a helpful way to examine your code as it runs. By pausing the code at certain points and going through it step by step, you can see how things change and identify problems.

Adding breakpoints

You have the ability to set breakpoints by selecting a node, which opens the node toolbar, and clicking the breakpoint icon (or use the hotkey cmd/ctrl-b).

When the execution reaches that node, it will pause (indicated by a striped blue outline).

Node outline when stopped at a breakpoint

With the buttons in the node toolbar or the Processes panel, you can step to the next node or continue the execution. If multiple processes are paused simultaneously, you can easily switch between them by clicking on their respective entries in the panel.

In the video below you can see what step debugging looks like. It also illustrates the (perhaps surprising) order in which the nodes are called in, where execution jumps directly from the top-left Log node to the Add node, before going to the second Log node.