A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
Check these areas in order:
- Confirm the trigger is not being skipped
- In Power Automate, go to My flows and open the flow.
- In 28-day run history, select All runs.
- If the expected run shows the trigger check was skipped, the trigger condition was not met.
- Edit the flow, open the trigger card, and review Settings > Trigger conditions. If custom trigger conditions exist, verify they match the values being created in the SharePoint item.
- Check whether the trigger itself is failing to register
- Open the flow Details page.
- If it shows There’s a problem with the flow’s trigger. Fix the trigger., the trigger registration failed.
- A common cause is that Power Automate service endpoints are not in the network allowlist. If applicable, have IT verify the required Power Automate IP addresses and domains are allowed.
- After fixing that issue, edit the flow and save it again so Power Automate retries trigger registration.
- Verify the connection used by the flow
- In Power Automate, go to More > Connections.
- Find the SharePoint connection used by the flow.
- If the connection is broken, select the link in the Status column and repair it.
- Expired passwords or expired authentication tokens can break the connection and prevent triggers from firing.
- Check for a data loss prevention (DLP) policy
- If the flow violates a DLP policy, the flow can be suspended and the trigger will not fire.
- Try editing and saving the flow. The flow checker can report a DLP violation.
- If blocked, an admin must review the tenant-level or environment-level DLP policy and update it.
- Review SharePoint trigger scope limitations
- If the trigger is actually monitoring a library scenario such as When a file is created or modified, note that SharePoint triggers do not fire for files added or updated in a subfolder. In that case, separate flows are needed.
- For a SharePoint list item created trigger, verify the flow is pointed to the exact intended list.
- Re-save the flow
- If the flow or environment was changed recently, edit the flow and save it again. This can restore trigger behavior in some cases.
- If the trigger is delayed rather than completely failing
- A communication problem or service issue can delay trigger execution.
- Check Help + support in the Power Platform admin center for active outages.
- Clear the browser cache and test again.
A practical first path is:
- Check All runs for skipped checks.
- Repair the SharePoint connection.
- Open Details and look for the trigger error.
- Edit and save the flow again.
- If still not firing, have an admin check DLP policy and network allowlisting.
References: