Power Automate's desktop flow schedules: checks for NZ RPA teams

What Microsoft released

Microsoft published its October/November 2026 Power Platform feature update on 10 November. The update includes several changes for teams that run Windows desktop automation (robotic process automation, or RPA) through Power Automate. The biggest is scheduled triggers. A desktop flow can now run on a recurring timetable set up in Automation center, with no cloud flow wrapped around it. Desktop flow templates let makers save standard error handling and logging as a starting point for other makers. Flowchart mode shows a desktop flow as a canvas of connected nodes. A new "When an alert fires" trigger in the admin connector can send Power Platform monitoring alerts to a Teams channel or create Azure DevOps work items.

Scheduled triggers and flowchart mode are both public previews. The scheduled triggers documentation says the feature is reaching regions gradually and isn't meant for production use. Microsoft hasn't published a general availability date. The desktop flow templates documentation has no preview label and needs Power Automate for desktop version 2.72 or later.

Why scheduling matters for operations teams

Microsoft's unattended desktop flow guidance describes cloud flows as the way to start unattended desktop flows. So a bot that rekeys supplier invoices into an old finance system at 6am every weekday has needed a separate cloud flow whose only job was to start it. After a few years, organisations end up with a pile of these wrapper flows. Each one belongs to whoever built it, and there's no central view of the timetable they create together.

The new Scheduled triggers page lists every schedule with its run mode, target machine or machine group, and connection reference. An Upcoming tab shows the projected runs. An operations lead can now see in one place what the bot machines will do overnight, and that view is useful for capacity planning and change control.

The Operator role is the other change worth noting. Microsoft's documentation says users with the Power Automate Operator role can create, edit, enable, disable and delete desktop flow schedules without permission to change the flow itself. A service desk could pause the overnight run when a target system is down and leave the automation logic alone. The Operator role's permissions on the trigger tables apply across the whole environment, beyond records the operator owns, so assign the role carefully. If your team already runs changes through a service management process, those schedule controls belong in the same process. Our ITIL 4 service management page covers that approach.

Details that will catch NZ teams out

Scheduled triggers run on Azure Logic Apps recurrence scheduling. Microsoft warns that daylight saving changes can make some local start times invalid or ambiguous. The Logic Apps scheduling guide suggests avoiding start times between 2am and 3am and choosing a time zone so the underlying UTC schedule shifts with the season. New Zealand's daylight saving ends on Sunday 4 April 2027 at 3am, when clocks go back to 2am. A job set for 2:30am Auckland time will meet 2:30am twice that morning. Daylight saving starts again on 26 September 2027 at 2am, and that morning has no 2:30am at all. Any batch job scheduled between 2am and 3am should move.

Missed runs aren't recovered. If the trigger or the service is unavailable, or someone disables the schedule, the missed runs are skipped and the schedule picks up at the next one. For a nightly bank file or payroll import, a skipped run needs a person or a monitoring alert to catch it. Weekly schedules need setting up at least seven days before the first intended run, or the first run might be skipped.

Environment restores need a manual step during the preview. Microsoft says scheduled triggers don't stay in sync when an environment is restored and can keep firing or fail to resume. Admins have to disable every scheduled trigger before a restore and re-enable each one afterwards. Teams that restore sandbox or test environments regularly should add that step to their runbook.

Licensing and machine rules haven't changed. Unattended runs still need the Power Automate Process plan. A Windows 10 or Windows 11 bot machine won't start an unattended run while any user session is signed in, even a locked one. The schedule can be correct and the run can still fail if someone left a session signed in on the bot machine overnight.

Templates and flowchart mode

A flow built from a template is an independent copy. Microsoft's template documentation says later template changes don't flow through to existing flows. If your team fixes a logging bug in the standard template, every flow built from the earlier version still has the bug until someone fixes each one by hand. A simple register of which flow came from which template version will save time later.

Flowchart mode helps with long flows that branch, because each path is visible on the canvas. The flowchart mode documentation lists two limits. A flow can switch into flowchart mode only when it has no errors. Dragging a node to a new spot on the canvas leaves the execution order unchanged, and Reorder is the command that changes it. A maker who confuses the two could approve a flow that doesn't run in the order shown on the diagram.

What we'd do now

• Export a list of the cloud flows whose only job is to start a desktop flow on a recurrence. Those are your candidates for scheduled triggers once the feature reaches general availability.
• Try scheduled triggers in a non-production environment if the preview has reached your region. Pick a non-critical flow and select the Auckland time zone explicitly.
• Move any scheduled run between 2am and 3am local time to another time before 4 April 2027.
• Set up alerting for skipped or failed runs. The new "When an alert fires" trigger can post monitoring alerts to a Teams channel your support team already watches.
• Add "disable scheduled triggers" to the environment restore runbook for as long as the feature stays in preview.
• Decide who gets the Operator role, and record schedule changes the way you record other production changes.
• If you adopt templates, version them and keep a list of flows built from each version.

Scheduling is the main weakness in many desktop automation setups. The preview gives teams a central schedule to manage, and the daylight saving, restore and licensing limits above still need handling. Our process and automation team can help review an existing Power Automate estate before you move schedules across.