HTTP Webhook action in Azure Logic App is stuck at running

dc2k79 0 Reputation points

Hey Guys,

Can anyone help on the issue of HTTP Webhook getting stuck forever in Azure logic app. I have checked previous posts where this question has been answered but nothing is conclusive. I am not sure if I am structuring the parameters wrong or something is missing. Every time playbook is run, it runs the logic but then does not go beyond the webhook and neither are any status codes returned because it just freezes there.

Any help would be appreciated.


Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
2,839 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Mike Urnun 9,666 Reputation points Microsoft Employee

    Hello @dc2k79 - Thanks for reaching out & posting on the MS Q&A!

    Because this issue is quite generic and without any specific errors to work with, it's best to open a support case and work with one of our support engineers in a 1:1 setting to troubleshoot the root cause. The most common causes we observe are as follows:

    • Scaling issue with the underlying instances due to Webhook being overloaded with a high volume of requests during a specific period of time.
    • Webhook was timed out (over the duration of 1hr) due to an uptime issue at the subscribing endpoint side.

    Troubleshooting requires analyzing the logs for the specific period of time when the failure started reporting, and it may be best to do this with one of our support engineers who has deeper insights into your unique environment. If your Azure subscription currently doesn't carry a support plan to open a case, let me know and I can help grant your subscription with one-time support (free of charge) for resolving this issue.

    In addition, I agree with your feedback on how there is an inconclusive and scarce amount of information when dealing with Webhooks that are in hanging/stuck status, but there could absolutely be a general guidance covering the common causes via one of our official docs. As such, please consider opening a doc issue by using "This Page" button located under one of the docs below. This will create an internal work item for us & help us prioritize it better:

    0 comments No comments