Try

error-handling.try Error Handling v0.1.0

Wrap nodes in an error-handling boundary: catch any failure, retry, and route success/error.

The Try step on the Studio canvas — The **Try** step as it appears on the Studio canvas — input pins on the left, output ports on the right.

Finding it in the library

Search the builder's node library for Try (it lives under Error Handling). A single click opens the in-editor docs panel shown here — description, ports, and every property, without leaving the canvas. Double-click (or drag) to add it to the workflow.

Try in the node library, with the in-editor docs panel open — The library entry and the in-editor docs panel for **Try** — the same reference this page is generated from.

Wired up in the builder

Try in a real, runnable flow — captured live from the Studio editor, exactly as it looks on your canvas. This is the same workflow used for the example input & output below.

Try wired into a runnable workflow in the Studio builder — **Try** wired into a runnable flow — input on the left, output on the right.

How it’s configured

The node’s settings as the builder shows them — every field laid out with real values. In the Studio these are edited on the node: click the chevron on the divider under its ports to open them.

The Try node's settings in the Studio builder — The settings for **Try**, showing the values from the flow above.

Ports

Ports are the node’s contract with its neighbours. In the editor a port label renders bold when wired and italic when optional; ◈ ports accept attachment carriers rather than data wires.

Direction	Port	Label
Input	`result`	Input
Output	`success`	Success
Output	`error`	Error
Output	`finally`	Finally

How data flows through it

Try consumes the content of the incoming envelope — when it is fed directly by a trigger, the trigger’s wrapper is unwrapped at the node boundary so the node sees the actual data, not the metadata shell. Its output becomes the payload for the next node, while the envelope (trace ids, correlation, binary refs) rides along untouched. In the Runs view you always see the whole envelope for both sides of this node.

Expressions in the config

None of this node’s properties are string-typed, so {{ }} expressions don’t apply here — JSON- and code-typed fields are always taken literally.

Build it with AI

Every node in this reference is reachable through Flowdrome’s AI Copilot and the MCP tools — say what you want, and the graph surgery happens server-side. Node types resolve fuzzily, so the catalog label (Try) works as well as the exact type id (error-handling.try).

In the Copilot panel (or any connected AI):

add a try node after the trigger

As a step in a create_chain_workflow call:

{"type":"Try","config":{}}

Raw MCP call — add this node to a workflow with add_node

curl -s -X POST http://localhost:4800/mcp -H "content-type: application/json" -d '{ "jsonrpc": "2.0", "id": "1", "method": "tools/call", "params": { "name": "add_node", "arguments": { "workflowId": "<id>", "type": "Try" } } }'

Example input & output

Captured from a real test run of the workflow above — this is what the Runs view shows after pressing Test workflow.

The framed member step throws on purpose; Try retries it, catches the failure, and emits it on the error port.

On this run the node emitted on port error.

Input — what the node received

The Try node's input envelope in the run data viewer — The input envelope in the Runs view — Flowdrome always shows the whole envelope, with the payload inside `body`.

Output — what the node produced

The Try node's output envelope in the run data viewer — The output envelope after the step ran.

Property reference

Every setting, with its type and default — the same fields shown configured above.

Property	Type	Default	Description
Retries `retries`	`int`	`2`	How many times to re-run a failed node inside this block before giving up and firing the error output.
Retry delay (ms) `retryDelayMs`	`int`	`0`	Delay between retry attempts, in milliseconds.

Related nodes

The rest of the Error Handling group — the same folder you’d scan in the editor’s library.

This page is generated from the node registry by gen-node-docs.mjs on every site build — ports, properties, defaults and visibility rules cannot drift from the code. The screenshots and example data are captured from a live Flowdrome by npm run shots:nodes and npm run gen:examples.