Debugging
Debug mode, the Messages panel, breakpoints, Continue and Step, and the Debug message step.
Debug mode
Switch on Debug mode in the header menu. The editor takes a debug lease on this flow from the hub, and the Messages panel at the bottom narrates every run of the published flow: which step fired, what each condition evaluated to, what each action did.
Only one editor holds the lease for a flow at a time; closing the flow or turning debug mode off releases it.
Breakpoints
In debug mode every step shows two small dots: on its left edge (before the step runs) and its right edge (after). Click to toggle. When a run reaches a breakpoint the hub pauses it and the Messages panel shows the state so far. Use the panel's buttons, or the keys:
| Action | Button | Key |
|---|---|---|
| Continue to the next breakpoint | Continue | F8 |
| Run one step | Step | F10 |
| Stop the run | Stop | — |
A paused run resumes on its own after a maximum pause so a forgotten breakpoint cannot park a flow forever. Breakpoints are editor state, remembered per flow on this browser; they are never part of the flow and never affect other users.
Debug message step
The Debug message Then step writes a line (with placeholders, and optionally a device's current state) to the Messages panel only. Unlike Log, nothing is recorded in Recent runs, so it is safe to leave in a flow.
Reading a run
Typical things to look for:
- a condition that evaluated to false where you expected true: check its Now: reading and
the units (
74versus74°F); - a step that never appears: nothing leads to it, or an earlier Stop ended the path;
- an action marked failed: the device rejected the service (unsupported option, device offline); the run still continues past it.