Power Automate desktop flows get three changes in the October/November 2026 Power Platform feature update: reusable templates, scheduled triggers that run desktop flows without a cloud flow, and a flowchart mode in the designer. Scheduled triggers and flowchart mode are in preview and rolling out gradually by region. Together they make desktop automation faster to build and simpler to run, and they shift a few responsibilities that RPA teams should plan for.
Templates: standards that do not update themselves
Desktop flow templates let a team capture patterns such as error handling and logging once and reuse them. A template is saved from the designer with File, Save as, Template, must be published before it appears in the template picker, and is shared from the portal with co-owner or read-only user permissions. Power Automate for desktop version 2.72 or later is required.
The governance detail is in the versioning model. Each flow created from a template is an independent copy. Editing or republishing a template “doesn’t change existing flows,” and deleting a template does not affect them. Templates are a good way to start every new bot on your standard error handling, but they are not a way to fix fifty existing bots at once. Keep a register of which flows were created from which template version, so you know what to revisit when the standard changes.
Scheduled triggers: no cloud flow in between
Scheduled triggers run a desktop flow on a recurrence in attended or unattended mode, configured in Automation center under Manage, Scheduled triggers (Preview). Each trigger uses a connection reference that targets a machine or machine group in the same environment, and the Upcoming tab shows projected runs.
Three behaviors deserve attention:
- Missed runs are skipped. If the trigger was disabled, the start time was in the past, or the service was unavailable, the occurrence is not run later. Processes with a hard daily deadline need monitoring, not just a schedule.
- Operators can manage schedules. Users with the Power Automate Operator role can create, change, enable, disable, and delete desktop flow schedules in the environment, without permission to change the flows. That is a useful separation of duties for operations teams, and a role to grant deliberately.
- Environment restores need a runbook step. During preview, triggers do not sync on restore. Microsoft’s guidance is to disable all scheduled triggers before a restore and re-enable only the ones you want afterward.
Credentials can be entered directly in the connection reference or taken from Windows credentials. For unattended bots, the identity behind that connection is the one to review; Service Principal Owned Flows covers the ownership side of the same problem for cloud flows.
Flowchart mode: easier to read, easier to review
Flowchart mode shows actions as nodes and execution paths as edges, with branch nodes for If and Switch and loop-back edges for loops. During debugging, nodes show running, success, or error states, breakpoints sit on the node toolbar, and Run from here starts a flow at a chosen action. Changes in flowchart mode and the default sequence mode carry over in both directions, and a flow can switch to flowchart mode only when it has no errors.
The benefit for governance is readability. A reviewer who is not the author can follow a complex bot’s paths far more easily as a diagram than as a numbered list of hundreds of actions. Consider making flowchart screenshots part of code review for complex flows.
What to standardize
- A small set of approved templates, owned by the RPA team, with a version noted in each flow’s description.
- Who holds the Operator role in each environment.
- Monitoring for scheduled runs that matter, since missed runs are not retried.
- A restore runbook step for scheduled triggers while the feature is in preview.
What the documentation does not cover yet
As of November 10, 2026, the templates page does not say where templates are stored, whether connections or credentials travel with them, or whether the feature is in preview. The scheduled triggers page names licensing for the run mode as a prerequisite without detailing it, and gives no limits on the number of triggers.
Sources
- What’s new in Power Platform: October/November 2026 feature update, Microsoft Power Platform Blog, November 10, 2026
- Create and use desktop flow templates, Microsoft Learn
- Schedule desktop flows with scheduled triggers, Microsoft Learn
- Flowchart mode in Power Automate for desktop, Microsoft Learn