Incoming webhook request never sends response and message delivered after hours

Rizqy 30 Reputation points
2023-07-10T09:44:38.1333333+00:00

Hi, we have issue with incoming webhook on our teams.

First, the webhook request took forever and never sends a response back. It happened since like 2 weeks ago and getting worse. When I tried to send the request manually with Insomnia, I got the same result: no response. To anticipate it, we set a timeout to 10 seconds to prevent it from causing another issue on our system. On Insomnia, I need to cancel the request manually.

But surprisingly, the message was appearing on the Team's channel several hours later. All the webhook sent from the systems and Insomnia are present, but the orders are at random times. Later messages can appear first and vice versa. Sometimes they don't show at all.

Second, we tried to create a new webhook within the same channel, trying to isolate the issue. We assume the issue was related specifically to a webhook endpoint. Then we test the new endpoint with Insomnia. The result was the same as above. The request never ends and the message appeared hours later.

Third, we set up a new webhook in a new channel. Here we tried to isolate whether the issue was related to a specific channel or not. Again, the result was the same.

So, I guess this is our last effort bringing it up here. We suspect the issue was out of our hands. Please help.

Microsoft Teams
Microsoft Teams
A Microsoft customizable chat-based workspace.
10,085 questions
Microsoft Teams Development
Microsoft Teams Development
Microsoft Teams: A Microsoft customizable chat-based workspace.Development: The process of researching, productizing, and refining new or existing technologies.
3,250 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Verakorn Suwansawhang 5 Reputation points
    2023-10-17T07:48:32.6633333+00:00

    We have the same issue. Do you have any solved answer.

    for more information - it always got timeout when call webhook and i don't think it's the network problem because when we call without payload, it's return payload error and not timeout.

    update - the next day, everything back to work! The messages we've sent and got timeout yesterday that appear delay after hours.

    1 person found this answer helpful.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.