Hello,
We have several webhooks Flows that we're now being prompted to switch to a new URL, and those URLs have been coming in throughout the past week or so. Switching to these new endpoints in other Flows that call them has worked fine except for instances where we want the parent Flow (the one with the http trigger) to be asynchronous. For example, we have a webhook Flow that can be called to refresh Power BI datasets or dataflows. The calling Flow would call that endpoint using an http action, provide some parameters like group id and dataset id, and then the webhook Flow would go refresh that dataset. The calling Flow effectively waits until until the webhook Flow completes that actions and provides a response back (asynchronously).
This all works fine with the old webhook URLs. When I try the same actions with the new URLs, the webhook flow is successfully triggered but a 404 response is immediately recorded by the calling Flow. It's not attempting to wait for the asynchronous response at all, and this seems like a bug on Microsoft's end. Is anyone else experiencing this issue?
212
Share
Report
All responses (
Answers (
