Help for owners
My SharePoint flow broke after someone changed the list
Short answer
A SharePoint flow usually breaks because something it points to changed: a list or library was renamed, a column was changed, a permission was removed, or the connection behind it expired. Microsoft lists 404, 403 and 401 errors for these cases. Open the failed run, read the first red step, and note what changed on that day.
Does this sound like your situation?
- A flow that ran every day has not run since somebody edited the list.
- The run history shows a red step with 404, 403 or 401.
- The flow runs but the new item has empty or wrong values.
- Files moved into a library no longer start the flow.
- The person who built the flow has left or changed role.
Why does this happen?
The list, library or site was renamed or moved
Microsoft's connection guide lists a renamed SharePoint list as a cause of 404 errors on every action that targets it. The flow points at the old name and has to be updated to the new one.
Confirmed by learn.microsoft.com
A column changed and the flow reads the wrong field
The same guide says SharePoint internal column names differ from the names people see on screen, so a column rename or a new column can leave an action succeeding but returning empty or wrong data.
Confirmed by learn.microsoft.com
Permissions or the connection changed
A 403 means the account behind the flow lost access to the site, or an admin policy now blocks it. A 401 means the stored sign-in no longer works, for example after a password or sign-in policy change. Microsoft says a connection owned by someone else needs that person to sign in again.
Confirmed by learn.microsoft.com
The trigger does not fire for the way files arrive
Microsoft states that moving files between libraries, or syncing files, does not change their modified date, so it does not start flows. It also notes that flows for lists only work on generic lists and document libraries, and that the flow checks for changes periodically, so runs can lag.
Confirmed by learn.microsoft.com
Power Automate switched the flow off
Microsoft documents that a flow with continuous failures is turned off after 14 days, and that a flow not triggered for 90 days might be turned off unless its owner has certain licences. If the owner leaves, the flow reverts to the Low performance profile.
Confirmed by learn.microsoft.com
What can I do about it today?
- Check whether the flow is onOpen the flow's details page and look at its status: On, Off or Suspended. Do not edit anything yet.
- Open the run history and find the first failed runWrite down the date, the red step and the error text. A 404 points at a renamed or deleted item, a 403 at permissions, a 401 at the connection.
- Ask what changed on or just before that dateA renamed list, a changed column, a new site structure, a password reset, a person leaving. One honest answer here saves hours.
- Do not delete and recreate the flowThe run history and settings are the evidence. A copy built in a hurry often repeats the same fault.
- Tell the people using the listItems added while the flow was broken did not go through it. Ask them to keep a note of what was added since the break, so nothing is lost.
When should I bring someone in?
- The error is still there after the connection is signed in again.
- The flow touches approvals, invoices or customer records, and missed items matter.
- Nobody knows who built the flow or which account owns it.
How do I handle it?
- Read the first failureI start from the first failed run and the step, not from the latest error, because later errors are usually side effects.
- Compare with what changedI line up the failure time against list, column, permission and licence changes, and check the flow's owner and connections.
- Fix on a copy with test itemsI repair the flow on a copy, using test items, and replace hardcoded names with lookups where the platform allows it.
- Catch up the missed itemsI list the items that arrived during the gap and push them through once, checking they are not doubled.
- Add a failure alertI add a step that tells a named person when the flow fails, so the next break is seen on the day.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Why did it break when nobody touched the flow?
Flows depend on things outside them: a list name, a column, a site permission, a sign-in. Changing any of those can break a flow that was never edited.
Can a flow turn itself off?
Yes. Microsoft documents that a flow with continuously failing steps is turned off, and that a flow that is not triggered for a long time might be suspended. Check the status on the flow page.
Will the missed items run by themselves?
Not by default. Items created while the flow was failing need to be checked and sent through again.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.