Power automate flow not triggering when a sharepoint item is created

SAMUEL J 0 Reputation points
2026-11-10T17:59:50.02+00:00

I'm setting up a simple Power Automate flow to send an email notification whenever a new item is added to a SharePoint List. I used the When an item is created trigger and selected the correct SharePoint site and list. However, after adding a few new items to test it, the flow doesn't seem to run at all. It's turned on, and I've double-checked the trigger settings, but there are still no new entries in the run history. I'm not sure what I'm missing here.

Could someone guide me on what I should check to figure out why the trigger isn't working?

Microsoft 365 and Office | SharePoint | For business | Windows
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Chris-D 2,700 Reputation points Independent Advisor
    2026-11-10T18:20:23.76+00:00

    Hi SAMUEL,

    Thank you for sharing the details of your situation.

    Since there are no entries in the flow’s run history, the issue is likely occurring before the email action, meaning the SharePoint trigger is not being activated.

    Here are some steps you can try:

    1. Open the flow and confirm that the Site Address and List Name selected in the When an item is created trigger are correct.
    2. Go to Data > Connections in Power Automate and check whether the SharePoint connection requires you to sign in again or select Fix connection.
    3. Open the trigger’s Settings and check whether any Trigger conditions are configured. If so, temporarily remove them and test the flow again.
    4. Confirm that the account used by the SharePoint connection still has access to the site and list.
    5. Save the flow, turn it off, wait a moment, and then turn it back on.
    6. Select Test > Manually, then create a completely new item directly in the SharePoint list. Editing an existing item will not activate the When an item is created trigger.

    If the trigger still does not run, I recommend creating a temporary test flow with only:

    • When an item is created
    • A simple Compose action using the item’s ID or Title

    This will help determine whether the issue is with the SharePoint trigger or another action in the original flow.

    For additional troubleshooting guidance, you may also refer to the following Microsoft article: Troubleshoot common problems with Power Automate triggers

    If you require more in-depth guidance or assistance with these steps, I recommend posting your question in the Microsoft Power Platform Community Forum. This is a dedicated channel for Power Automate discussions. I suggest posting a new topic there because resources and expertise related to Power Automate are limited in the general Q&A forum. In the Microsoft Power Platform Community Forum, you can connect with experienced Power Automate users and specialists. Other community members and partners who regularly participate in the forum may also share their knowledge and benefit from the discussion.

    User's image

    I hope this information is helpful. Should you have any further questions or need additional assistance, please feel free to share them in the comment below. I'm very happy to help.  

    If the answer is helpful, please click 'Yes' and kindly upvote it.

    Note: Please follow the steps in the forum documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-11-10T18:00:06.5266667+00:00

    Check these areas in order:

    1. 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.
    2. 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.
    3. 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.
    4. 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.
    5. 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.
    6. 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.
    7. 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:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.