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

In Maestro BPMN, two new activities are available for Orchestrator queue-based processes. Get queue items queries items on a queue by status, reference, creation date range, or priority, without dequeuing or locking them, making it suitable for read-only checks and conditional branching. Wait for queue event, available on a receive task or an intermediate catch event, blocks execution until a transaction item becomes available on a queue, then surfaces the dequeued item's fields as process outputs.

For more information, see Queue task activities.

In Maestro Flow, Autonomous Agent nodes now support richer control over Model Context Protocol (MCP) tools. You can edit per-argument descriptions, view a tool's full input and output schema, and choose how each argument gets its value: the agent decides at runtime, it's bound to an agent variable, or it's a fixed value that can be marked sensitive. MCP servers now also expose an explicit Refresh tools action instead of only discovering tools automatically, and can pull their tool list live from Agent Hub.

For more information, see Agent.

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.

In Flow, the Decision node's True branch can now be left unconnected, matching the existing behavior of the False branch and the Switch node. When a branch has no downstream nodes, Flow automatically completes it instead of failing at runtime with a path-not-found error.