# August 2026

> August 2026 release notes for Maestro in Automation Cloud and Test Cloud.

## August 20, 2026

### Edges route around nodes after auto-layout

In Flow, running **Tidy up nodes** or **Tidy selected** now routes edges around nodes instead of straight through them, producing cleaner diagrams when nodes are repositioned. You can also drag an edge segment to reposition it — the adjusted path is kept for the session without affecting the saved document or the undo history.

Loop edges (self-connections and loop-back handles) continue to use their existing handle-based routing and are unaffected by this change.

For more information, see [The canvas](https://docs.uipath.com/maestro/automation-cloud/latest/user-guide/canvas-overview).

### Decision node's True branch is now optional

In Flow, the [Decision node's](https://docs.uipath.com/maestro/automation-cloud/latest/user-guide/node-decision) **True** branch can now be left unconnected, matching the existing behavior of the **False** branch and the [Switch node](https://docs.uipath.com/maestro/automation-cloud/latest/user-guide/node-switch). When a branch has no downstream nodes, Flow automatically completes it instead of failing at runtime with a path-not-found error.

### Bug fixes

- In Flow, downloading an attachment during a debug session no longer stops execution polling. Previously, browsers could interrupt the debug session when a file download started even though the page stayed open.
- In the VS Code extension, downloading a flow execution attachment now opens a native save dialog instead of attempting to navigate to a signed URL that the extension's webview doesn't support.
- In Flow, dropping or inserting a variable into a multi-line script editor now produces a bare path (for example, `$vars.value`) instead of `{{ $vars.value }}`, which was a syntax error in JavaScript and TypeScript contexts.
