# 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.

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](/midio-docs/reference/overview/processes.md), 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`](/midio-docs/built-in-nodes/core-std.md#log-std) node to the [`Add`](/midio-docs/built-in-nodes/core-std.md#add-1) node, before going to the second [`Log`](/midio-docs/built-in-nodes/core-std.md#log-std) node. {% embed url="" %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.midio.com/midio-docs/guides/debugging.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.