Why a flow that ran for a year stops on a Tuesday
A flow is a chain of steps, and each step reaches into another system through a connection that belongs to somebody. The flow itself may not have been edited since the day it was built and still fail, because the account behind one connection changed its password, the other system renamed a field, or a sign-in policy changed underneath it. Most Power Automate maintenance is not fixing the flow’s logic; it is keeping its connections, owners and the systems on either end in step with each other.
The first job on any failure is finding out what actually went wrong. Microsoft’s guide to troubleshooting a cloud flow (opens in new tab) walks through the 28-day run history, and separates authentication failures (an “Unauthorized” message or a 401 or 403 code, usually fixed by repairing the connection) from action configuration errors (a 400 or 404, fixed by correcting the flow) and temporary 500 or 502 errors that a resubmit clears. Resubmitting without knowing which of the three you are looking at is how one failure quietly becomes a month of them.
What this covers, and what it deliberately does not
Support here means keeping flows that already work running, and improving them in small steps. The line matters because a request on the wrong side of it needs a different engagement, and pricing it as maintenance would hide its real cost.
| The request |
Handled as support? |
Notes |
| An approval, scheduled or integration flow has failed or fails intermittently |
Yes |
Run history read, cause fixed, error handling added so the next failure notifies someone |
| Flows broke after the maker left or changed a password |
Yes |
Ownership and connections moved to accounts that will still exist; co-owner named |
| A desktop flow stopped after a PC was reset, rebuilt or updated |
Yes |
Machine re-registered, connection repaired, broken steps re-recorded |
| A premium-connector licence warning after an ownership change |
Yes |
Licensing checked against how the flow runs; options set out before anything is switched |
| An extra approver, a new schedule or one more field sent to another system |
Yes |
Batched into a written change list at one fixed fee |
| The flow is triggered from inside a Power App |
Yes, alongside the app |
The app and its flows are supported together — see Power Apps support and maintenance services |
| A new automation for a different process |
No |
That is a build — see Power Automate consulting |
| Flows that never worked, or a build that stalled halfway |
No |
That is a takeover — see Power Platform project rescue services |
| A 24/7 on-call desk with a guaranteed response time |
No |
We do not offer a service-level agreement; a managed service provider is the right fit for that |
Not sure which approach suits your flow fixes and changes? A senior engineer will talk it through with you, at no cost.
Talk to an engineer →
Flows on their own, or flows inside an app
Many flows have no app at all. An invoice approval starts when a file lands in a SharePoint library; a nightly job copies new orders from one system into another; a weekly flow emails a summary to the managers. Nobody opens anything to use them, so nobody sees them fail. This service is built for those flows. If your flows are triggered from a canvas or model-driven app and the two are maintained together, our Power Apps support and maintenance services cover the app and its flows as one piece of work, and that page also sets out where Microsoft’s own support ends and a partner’s begins.
The same approach applies elsewhere in the platform. If the thing that needs looking after is a live dashboard, the equivalent is Power BI support and maintenance services; if it is the SharePoint site your flows read from and write to, see SharePoint support and maintenance.
Ownership, licences and the flow nobody owns
Every flow has an owner, and by default it is whoever built it. Microsoft’s guide to changing the owner of a cloud flow (opens in new tab) sets out three details that catch small businesses out. Ownership can only be changed in place on a flow that sits inside a solution; a flow built outside one has to be added to a solution or recreated. A scheduled or automated flow runs under its owner’s licence, so moving it changes whose licence it uses. And if the new owner has no premium licence while the flow uses premium features, Power Automate warns, keeps the flow running for 30 days, then turns it off.
That is why we check licensing before moving anything, not after. Which plan your flows need depends on the connectors they use and how they are triggered, and Power Automate licensing for small businesses explains the options in plain terms. We do not sell licences; we tell you what each flow needs and leave the purchase with you. If a maker has just handed in their notice, what happens when a Power Automate flow owner leaves sets out what to move before their account is disabled.
Desktop flows and the machines behind them
Desktop flows add a moving part that cloud flows do not have: a real or virtual Windows machine. Microsoft’s documentation on managing machines for desktop flows (opens in new tab) notes that a machine loses its registration when the PC is reset, that moving a machine to another environment removes all its current connections, and that maintenance mode lets you pause runs while the machine is updated. Any of those can stop a desktop flow without touching the flow itself. So can an update to the application the flow clicks through, when a button moves or a screen is renamed.
Maintenance for a desktop flow therefore covers the flow, the machine and the application together. If you are still deciding whether a task should be a desktop flow at all, desktop flows versus cloud flows compares the two.
Support priced per batch, not per month
The usual way to buy this is a monthly retainer for a set number of hours. We do not offer one. Flow maintenance is lumpy — nothing for two months, then three failures in a week after a password policy changes — and a flat monthly fee means paying for the quiet months while the busy ones still run over. Instead, each batch of fixes and changes is written down as a list of specific items, and the whole list carries one fixed fee you approve before work starts. When nothing has failed and nothing needs changing, there is nothing to pay. We do not publish a price list, because the fee depends on what is in the batch and how the flows are built; the quote follows the free consultation and, on the first batch, a read of the flows. How our fixed-fee process works is the same for a batch of fixes as for a full build.
Who this fits, and who it does not
The usual fit is a small or mid-size business with a handful to a few dozen flows in daily use — approvals, scheduled reports, integrations between systems, perhaps a desktop flow or two — built by a contractor, an agency or a capable colleague who has since moved on. The flows matter, nobody wants to rebuild them, and no one’s job is to keep them running.
It fits badly in two cases. If you need someone on call overnight with a contractual response time, that is a managed service provider, not us. And if the flows never worked properly, the honest answer is a rescue or a rebuild, and we will say so during the consultation rather than sell a string of fixes that will not hold. Work is delivered remotely across all US states from our Orange County, CA base, by senior US-based engineers.