Execution logs
Per-node testing, full-run history, and the log viewer panel.
Automations are easier to debug than agent conversations because each step is explicit and inspectable. Logs are how you actually see what happened.
Per-node testing
Every node has a Play icon (test) that appears on hover, left of the ⋮ menu. Clicking it runs just that node with its current inputs and shows the result in the left Logs panel.
For executable nodes:
- REST API Request — runs a real
fetch()(with optional CORS proxy), shows the built request (method, URL, headers, body) and the response. - Code — evaluates the JavaScript and shows the return value or error.
- Tool Call — invokes the tool with the current arguments.
- Condition — shows which branch would be taken.
- Prompt — calls the LLM with the resolved prompt.
For config nodes (Model, Identity, Sandbox, Tools, Sub-agents), the test validates the config but doesn't run anything.
The Logs panel
The left panel has two tabs:
- Logs — chronological list of test results
- Variables — current values of workflow variables
The Logs tab has a compact toolbar:
- Search filter
- Status filter dropdown (All / Success / Error / Info)
- Copy button — click any log to copy it; click Copy All to copy the entire history
- Clear button — flush the log history
Each log entry is collapsible. For HTTP and tool calls, the body renders as an expandable JSON tree (strings, numbers, booleans color-coded; arrays and objects collapsible with chevron toggles).
Drag the right edge of the panel to resize it (200–480 px). The drag handle highlights purple on hover.
Full-run history (planned)
Today, the Logs panel shows results of test runs in the editor session. Persistent per-run history (a record of every automation execution with status, duration, and inputs) is on the roadmap.
The underlying execution layer (automation-executor Edge Function)
already records run state to Supabase — the UI for browsing it across runs
is what's coming next.
Tips for debugging
- Test bottom-up. Start with the leaf nodes (Tool Call, REST API) so you know their results before testing parents.
- Use Notes. Drop Note nodes near tricky parts of the graph to remind future-you what's expected.
- Bind to test outputs. Once you've tested an upstream node, its output appears in the ƒ modal under Actions → [node] → output. Use it to wire downstream bindings.
- Inspect variable state. The Variables tab updates live during test runs — handy when a Change Variable node isn't doing what you expect.