Trying to understand how to setup webhooks in flow to convert an existing flow that sometimes times out but not always. Trying to distill it down to a simple example.
The real flow does stuff but its basically that.
So is converting this to Webhooks basically replacing the HTTP-HTTP action with HTTP-Webhook and setting the Subscribe URI to "Receivers" URL? I tried that, but Sender never got the message / stopped running and I had to cancel it.
Also what is the unsubscribe URI?
Hi @bbrazeau ,
Could you please share a screenshot of the flow when you replace the HTTP-HTTP action with HTTP-Webhook and set the Subscribe URI to "Receivers" URL?
Could you please share the run history of the flow when the sender don't get the message or stop running.
Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Sure, may be overkill but here are a few images to review.
So the basic Flow with the HTTP caller:
And the Receiver - I only have the delay at 5 seconds as I'm not testing the timeout.
Successful run returning the Success Message after the 5 second delay.
Everything works as expected. I then added a second HTTP action to the flow for the webhook call.
Running the flow, it triggers both calls to the receiver which were 5 seconds apart from the delay.
But looking at the Flow's activities, its stopped on the Webhook action
And the run history shows its well beyond the 5 second delay so the Webhook isn't reacting to the returned message.
Likely I have the webhook setup incorrectly.
Check out the new Process Advisor community forum board!
Check out new user group experience and if you are a leader please create your group
Participate in the Power Virtual Agents Community Challenge
Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.