Repository navigation
SharePoint webhook subscription #9089
Description
Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
None
What browser(s) / client(s) have you tested
- 💥 Internet Explorer
- 💥 Microsoft Edge
- 💥 Google Chrome
- 💥 FireFox
- 💥 Safari
- mobile (iOS/iPadOS)
- mobile (Android)
- not applicable
- other (enter in the "Additional environment details" area below)
Additional environment details
- browser version
- SPFx version
- Node.js version
- etc
Describe the bug / error
There seems to be an issue encountered while setting up a subscription for a SharePoint webhook. The problem is that the SharePoint Online list webhooks are not consistently firing as expected.
Steps to reproduce
The triggering of the webhook when a new item is created in the SharePoint list is not consistent.
Expected behavior
The desired functionality is that when a new item is created in the SharePoint list, the webhook should be triggered. This webhook is then consumed in Power Automate using an HTTP receiver.
Activity
Ryan365Apps commentedon Oct 11, 2023
Hello, has this been investigated. I'm seeing the same problem.
Ashlesha-MSFT commentedon Jul 8, 2025
hajiranazu,
I'm reaching out to check if this issue has been resolved on your end.
Since the steps to reproduce are currently a bit unclear, it would be helpful if you could provide detailed repro steps—including how the webhook was registered, how items were added to the list (e.g., via UI, script, or automation), and any patterns you've noticed when the webhook fails to trigger.
This will help us investigate further and determine if the issue is environment-specific or a broader platform behavior.
joostvdlinden commentedon Aug 29, 2025
Hello Ashlesha-MSFT , I also experience the exact same issue as the original topic starter.
I register the subscription by using a Logic App through the Send an HTTP Request to SharePoint Online (user delegated). The subscription is registered successfully.
I have implemented all logic of handling request as described here: https://gist.github.com/zplume/1baf04cc05927b57a5da248454b15dcc
List items are created through the interface in SharePoint Online (manually). The first one gets triggered just fine after creating the subscription, but the following will never trigger. My Logic App never receives a notification from the service.
joostvdlinden commentedon Sep 1, 2025
Ashlesha-MSFT I just discovered something interesting.
Last Friday I added two new list items to my list, the subscription did not send a notification to my Logic App (listening application) for those two new items. From that moment and during the whole weekend: silence.
Just yet I added another new item to the SharePoint list and surprisingly, this time I did received a new notification from the service. My Logic App was triggered and it pulled the three list item changes.
I wonder, why did it not send a notification for the other two items that were added last Friday? Those initial two items were created 25 minutes apart from each other.
joostvdlinden commentedon Sep 5, 2025
Last Monday I did some additional testing and I was surprised to see that every test led to a successful trigger of my Logic app.
I wonder, does it take time for the subscription (webhook) to provision in the SharePoint Online service and does this lead to inconsistent behavior for the first few hours after creating the subscription?
Ashlesha-MSFT commentedon Oct 14, 2025
Apologies for the delayed response.
Thank you for sharing the details. Since the delay issue you’ve mentioned is not documented in the SharePoint webhook subscription behavior, I will be escalating this to the engineering team for further investigation.
I’ll keep you updated on any progress or findings from their side.
VesaJuvonen commentedon Nov 3, 2026
This issue is more than 12 months old and has not had recent activity. We are cleaning up the backlog so we can manage incoming reports more efficiently. If the issue is still relevant, please submit a new issue with updated details and current reproduction steps. We apologize for any inconvenience caused by this updated process, and thank you for being part of the SharePoint developer ecosystem.
github-actions commentedon Nov 3, 2026
Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.
If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.
We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.