UiPath’s Maestro Flow became generally available on 17 September 2026, according to the company’s Maestro Automation Cloud release notes for September 2026, opened for this pack. Soft FLAG: the notes include an explicit correction that GA notes published on 15 September were in error and that the correct release date is 17 September — cite the corrected date. Soft FLAG: single primary source (vendor docs); no independent customer-count or revenue gate in the opened notes.
The product motion is a named canvas leaving preview for production support. Maestro Flow is the third canvas in Maestro Orchestrate, alongside BPMN and Case. General availability, the notes state, means Flow processes are supported for production use on the same Maestro engine as BPMN and Case, with the same durable execution and instance control — retry, cancel, pause, resume, migrate and go-to on live instances, individually or in bulk. Soft FLAG: “no cap on duration or concurrency” and multi-day wait/resume behaviour are vendor runtime claims.
What you compose on the canvas, per the notes: autonomous AI agents (including third-party agents over Model Context Protocol and Agent2Agent) with PII and prompt-injection guardrails; enterprise and custom connectors, HTTP, webhooks and wait-for-event steps; native Data Fabric read/create/update/delete nodes; inline document extract/summarize/classify; and human-in-the-loop Quick Forms and Action Apps delivered in Slack, Teams, email and Action Center. Soft FLAG: conversational chat/voice agents, inline Data Fabric entity modeling, coded-function nodes, Autopilot scaffolding and native document-processing nodes are listed under Preview in the same notes — do not treat those as GA.
Where you build: VS Code and forks (Cursor and others) via the Maestro extension, Studio Web, and Studio Desktop alongside RPA. Soft FLAG: on 16 September, “Build a Maestro Flow with a coding agent” also moved to generally available — coding agents author runnable `.flow` files through the `uipath-maestro-flow` skill / `uip` CLI; that is a second named usage gate in the same week, still vendor-documented.
Maestro Automate — a lightweight Flow-based runtime for short workflows lasting minutes or hours, with runs capped at 24 hours — shipped generally available on 18 September alongside Flow, the notes say. Soft FLAG: Automate vs Orchestrate licensing and instance-management differences are product-line detail; the desk lead is Flow’s production GA.
Named actor for the page is UiPath’s Maestro product organisation as reflected in the release notes; no executive quote block appears in the opened September notes page. Soft FLAG: absence of a named executive quote is a thin-colour note, not a defect in the GA fact.
What to watch without mood: first published production-instance or customer-logo disclosures after GA; whether Preview chat/voice and Autopilot features graduate with dated notes; any third-party MCP/A2A partner announcements that name Flow as the runtime.
Floor: Maestro Flow GA 17 Sep (notes corrected from 15 Sep erratum) — agents/APIs/robots/documents/humans on one canvas; production on Maestro engine; coding-agent .flow authoring GA 16 Sep; Automate GA 18 Sep (UiPath docs).