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

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / "When a HTTP request i...
Power Automate
Unanswered

"When a HTTP request is received" (GET) action triggering randomly from Facebook leads?

(1) ShareShare
ReportReport
Posted on by 503

Hi all 

 

This is a long shot post, but thought I would try my luck to see if anyone has encountered something similar. 

I have a flow triggered by the "When a HTTP request is received" (GET) action and it seems to be triggering randomly. Even when there is no reason for the trigger. 

 

The URL is linked up with a Facebook Webhook and subscribed to the "leadgen". It is monitoring Facebook Leads as they come through and it was working fine for the past week, up until I deployed into Production with a Managed solution. Since then, it seems to just trigger randomly based on past leads that have already come through hours or days ago... It really doesnt make sense to me, because I made no changes to the flow apart from updating the connections for the target environment. 

 

Thank you to anyone that has an idea. 

 

 

Categories:
I have the same question (0)
  • Michael E. Gernaey Profile Picture
    53,960 Moderator on at

    @Usernametwice23 

     

    A few things

     

    1. You should look at your entire pipeline, to verify that in fact there wasn't something coming in. Don't think hey no one was doing anything so no way. Make sure you have a way to verify that the WebHook and the upstream in fact haven't triggered it.

     

    2. Is there any kind of pattern, time of day, number of times per day it seems to do it?

     

    I am wondering if there is some retry logic happening in the WebHook, or based on the configuration of the upstream.

     

    3. Please share a run, with the inputs and outputs of the trigger where you believe it should not have.

     

    4. Lastly, make sure that data coming into the Flow has a TimeStamp  and that its generated in real-time, not some existing "created" column etc. That way, although it may look old, you will have a late one when it fact there is a bug upstream.

     

    5. Verify that you have no rogue runs happening, go to Details, Click the All Runs icon and then in the top right corner, filter by running

     

    6. Make sure you have no test apps that accidentally point to Dev and thats the issue. 


    If I have helped you, I would really appreciate if you please Mark my answer as Resolved/Answered, and give it a thumbs up, so it can help others

    Cheers

    Thank You
    Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
    https://gernaeysoftware.com
    LinkedIn: https://www.linkedin.com/in/michaelgernaey

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

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!

Leaderboard > Power Automate

#1
Haque Profile Picture

Haque 557

#2
Valantis Profile Picture

Valantis 328

#3
David_MA Profile Picture

David_MA 264 Super User 2026 Season 1

Last 30 days Overall leaderboard