What shipped this month

This release is all about clarity and speed in the builder. Branching is easier to read, big canvases are easier to navigate, and run logs feel instant instead of sluggish. Nothing flashy for the sake of it—just upgrades that reduce clicks and help you move from “hmm” to “done” faster.

Conditional branching you can read at a glance

Decision points now render with a clean diamond and labeled paths (success / else or your own short labels). Active paths are bold; inactive are muted so screenshots and quick reviews make sense. The net effect: fewer misroutes and less time tracing arrows across the canvas. If you’ve got older workflows, republish them and the new visuals apply automatically, no rebuild required.

Canvas minimap and smoother zoom

When workflows get wide, you shouldn’t feel lost. A bottom‑right minimap shows the whole canvas; drag to jump. Zoom now steps cleanly from 75% to 125% without blurry nodes or offset connectors. If you sketch ideas at 75% and finish at 100%, you’ll notice arrows stay crisp and hit the right targets.

Run logs that keep up

Logs now stream progressively and filter faster. Click a run and the first chunk appears quickly, with the rest filling in as it loads. You can jump to steps by name, copy inputs/outputs, and share a deep link with teammates. Flaky external calls are collapsed into a tidy retry stack so you see the story, not noise. Finding the “why” behind a failure should take seconds, not a detective shift.

Small things that add up

Connectors list your most used at the top. Step cards use clearer icons and spacing. Arrow snapping is snugger on dense canvases, and keyboard nudges feel more predictable. Status chips are stronger—Success, Warning, Failed—so you don’t squint to parse color alone. None of these change how you build, but together they cut friction you felt every day.

Migrating older flows

You don’t have to rebuild. Republish to pick up the new visuals; then test your run logs once to ensure filters behave as expected. If you relied on very long labels to explain logic, consider adding a one‑line description on the node and shorten the label. Your future self will thank you when you scan the canvas at speed.

Pro tips for this release

Use verbs in decision names (e.g., “Check tier ≥ Pro”). Keep the success lane short and route the else path around it to avoid crossing lines. Add a single alert on fail branches with an owner and a due date—threads are fine for discussion, but alerts should lead to one action. If a flow sprawls, split it: two small flows with a handoff are easier to reason about than a giant everything‑bagel.

What’s next

We’re exploring swimlanes you can name (e.g., Pro vs. Free), a compact node inspector, and a side‑by‑side compare for workflow versions. If you have a canvas that always feels one panel too big, send it—we’ll use it as a testbed. For now, enjoy the snappier builder and quicker logs, and let us know where the rough edges still are.