Running & Debugging Flows
Everything you build in the Flow Editor is executed with three buttons in the top-bar:
- ▶ Play
- ⏸ Pause / Continue
- ⏹ Stop
This page explains how those controls interact with the outline-colour system and the right-side Console tab, so you can run and troubleshoot flows with confidence.
1 · Play, Pause, Stop
▶ Play
Runs the flow. If the workflow is paused, it will run from the first block that is not already green.
This allows you to iterate quickly without having to start from the top every time.
⏸ Pause / Continue
Freezes execution at the current blue outline.
Press run to resume from that point.
⏹ Stop
• Clears all blue / green / red outlines.
• Resets internal state so the next Play starts at the very top.
2 · Outline colours
| Colour | Meaning |
|---|---|
| Blue | Block is executing right now. |
| Green | Block finished successfully during the last run. |
| Red | Block failed; an error entry appears in the Console. |
Green outlines persist until you press Stop.
That persistence enables the “resume from first non-green block” behaviour of Play.
3 · Typical run workflow
- Build or change a block.
- Stop (optional) if the block is already green.
- Play to test the change.
- Watch the blue outline advance; check the Console for output or errors.
- Repeat until everything is green with no red outlines.
4 · The Console tab
Open the Console (right sidebar) to see:
- Output from Message ▸ write to console blocks.
- Runtime errors thrown by any block.
- The most recent entry is always at the bottom.
5 · Saving your work
- The editor auto-saves whenever you press Play.
- Click the 💾 icon at any time for a manual save. It's a good idea to save often.
6 · Recap
- Play resumes from the first non-green block, Pause toggles execution, Stop resets everything.
- Blue / green / red outlines provide immediate status feedback.
- The Console is your single source for output and error details.
- Auto-save on run plus the manual 💾 button keep your flow versions safe.
With these tools you can iterate rapidly and fix issues as they appear—happy debugging!