web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Agent Academy Hackathon is happening now!
Welcome to the Power Platform Communities
News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / SharePoint trigger “Wh...
Power Automate
Unanswered

SharePoint trigger “When an item is created” intermittently stops firing (Webhook issue?)

(0) ShareShare
ReportReport
Posted on by JS-06021750-0

Hi everyone,

 

I’m experiencing an intermittent issue with the SharePoint trigger “When an item is created” in Power Automate, and all evidence points to a webhook problem rather than flow logic.

 

Context

  • SharePoint Online / Microsoft Lists
  • Power Automate flow using When an item is created
  • Flow worked correctly for several days
  • No changes to:
    • permissions
    • list schema
    • columns
    • SharePoint connection
    • environment (Default)
Issue behavior
  • The trigger stops firing completely
  • No errors appear in run history (it simply doesn’t trigger)
  • Get items using the same SharePoint connection works fine
  • Recurrence-based flows work correctly
  • Re-saving or recreating the flow sometimes makes it work again
  • After some time, the trigger fails again
Key observations
  • This looks like a SharePoint webhook subscription issue
  • No visible errors in Power Automate
  • Items are created in the list, but the flow never triggers
  • Behavior is inconsistent and intermittent
Questions
  1. Is there any known issue with SharePoint webhooks in Power Automate?
  2. Is there a way to force webhook re-subscription or refresh?
  3. Any diagnostics or logs available to confirm webhook invalidation?
  4. Is this expected behavior in corporate tenants with strict policies?

Any technical insight would be greatly appreciated.


Thanks in advance.
 

Categories:
Building flows
I have the same question (0)
  • David_MA Profile Picture
    David_MA 14,614 Super User 2026 Season 1 on at
    Since this was posted in February, hopefully you've resolved the issue. I have not experienced what you have described. However, sometimes when there is an issue with a trigger action, I have seen posts that suggest that you delete the trigger, add it back into the flow, and create a new connection reference for the trigger. Have you tried this?
     
    I assume you have no trigger conditions set up for the flow? If you do, have you checked to see if the trigger condition has been configured to meet your expectations? Having a trigger condition would account for why a flow would only sometimes trigger as that is the intent of trigger conditions.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Agent Academy Hackathon is happening now!
Welcome to the Power Platform Communities

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the April Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Vish WR Profile Picture

Vish WR 796

#2
Valantis Profile Picture

Valantis 568

#3
Haque Profile Picture

Haque 538

Last 30 days Overall leaderboard

Featured topics

Known issue with browser automation in Power Automate for Desktop on Google Chrome 146 and 147
Share your ideas and struggles with building Power Automate flows!
Survey: Power Automate mobile app
How to Ask for Help with Your Power Automate Workflow
Flows are not visible for users who sign in with their personal accounts
Start and wait for an approval action
Restore a deleted flow
List of actions cheat sheet for Power Automate Desktop
Welcome to the Power Automate forum!

Product updates

Microsoft Power Platform Community release plans