Power Automate Flow Not Triggering? 9 Things to Check
A flow that silently stops running is one of the most common Power Automate problems. Work through these checks in order; the first four solve most cases.
Awokunle Winner1. Is the flow actually on?
Open My flows and check the status. A flow can be turned off by hand, suspended by an admin's data policy, or switched off automatically. On some licences, Microsoft turns off flows that haven't triggered for a long period and emails the owner first.
Turn it back on, then check whether new items start runs.
2. Check the run history
Open the flow's details page and look at the run history. If there are failed runs, the flow is triggering and the problem is a later step: open the run and look for the red action.
If there are no runs at all, the trigger isn't firing. Keep going.
3. Look at trigger conditions
Open the trigger, go to Settings and check Trigger conditions. A condition such as @equals(triggerBody()?['Status']?['Value'], 'Pending') stops the flow for every item that doesn't match, and nothing appears in the history.
Remove the condition temporarily. If the flow starts running, fix the expression: column names are internal names and choice columns need ?['Value'].
4. Fix broken connections
Go to Data, then Connections, and look for anything marked 'Fix connection'. Password changes, MFA changes and expired sign-ins all break connections.
If the person who built the flow has left, their connections stop working. Add a co-owner and rebuild connections under a service account so this can't happen again.
5. Permissions on the list
The account behind the SharePoint connection needs at least read access to the list. If someone tightened permissions on the site or list, the trigger can stop without an obvious error.
6. Was the list renamed, moved or recreated?
Triggers point at the list's internal ID. If the list was deleted and recreated, or the site moved, reselect the site and list in the trigger even if the name looks right.
7. Give it a few minutes
SharePoint triggers check for changes on a schedule rather than instantly, so a few minutes' delay is normal. If you're testing, wait before assuming it's broken.
8. Watch for loops
A flow on 'When an item is created or modified' that updates the same item triggers itself again. Add a trigger condition that ignores changes the flow makes, for example by checking a status or a 'processed' column.
9. Data policies and licensing
If your admin blocks a connector with a data loss prevention policy, flows that use it are suspended. Premium connectors also need the right licence. The flow's details page usually shows a warning banner in either case.
Want this done for you?
I build this for clients every week. Book a free 30-minute call and I'll tell you exactly what your team needs.