Home

Error 500 by calling and creating a webhook connector

%3CLINGO-SUB%20id%3D%22lingo-sub-109723%22%20slang%3D%22en-US%22%3EError%20500%20by%20calling%20and%20creating%20a%20webhook%20connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-109723%22%20slang%3D%22en-US%22%3E%3CP%3ESince%20yesterday%20I%20get%20error%20messages%20while%20trying%20to%20call%20a%20Teams%20webhook%20of%20my%20channels.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22Webhook%20message%20delivery%20failed%20with%20error%3A%20Microsoft%20Teams%20endpoint%20returned%20HTTP%20error%20500%20with%20ContextId%20tcid%3D105260188274304390%2Cserver%3DEAP010211239200..%22%20Is%20the%20answer%20I%20get%20by%20running%20my%20demo%20scripts%20that%20worked%20now%20for%20a%20few%20months.%20I%20get%20this%20now%20on%20every%20webhook%20I%20configured%20at%20this%20tenant.%20All%20of%20them%20worked%20by%20Friday%26nbsp%3Bbut%20are%20broken%20since%20at%20least%20Saturday%20evening%20UTC.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAt%20first%2C%20I%20thought%20maybe%20something%20gone%20wrong%20with%20that%20tenant.%20Today%20I%20created%20a%20new%20Team%20in%20a%20different%20tenant%20in%20the%20web%20interface.%20I%20tried%20to%20create%20a%20webhook%20and%20boom%3A%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20721px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F20722i4A83A6A3AB8C8711%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22teamserror.png%22%20title%3D%22teamserror.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20at%20least%202%20tenants%20with%20error%20500%20while%20dealing%20with%20connectors%20in%20Teams.%20Anyone%20else%20getting%20these%20kinds%20of%20errors%20at%20the%20moment%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-109723%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-110032%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20500%20by%20calling%20and%20creating%20a%20webhook%20connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-110032%22%20slang%3D%22en-US%22%3E%3CP%3Eyeah%20same%20here%2C%20and%20the%20newly%20created%20webhooks%2C%20also%20work%2C%20no%20need%20to%20recreate%20them.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-110031%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20500%20by%20calling%20and%20creating%20a%20webhook%20connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-110031%22%20slang%3D%22en-US%22%3E%3CP%3ELooks%20like%20it's%20back%20to%20normal%20now.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAt%20least%20my%20Azure%20Functions%20trigger%20my%20connectors%20again%20and%20I%20get%20the%20messages%20in%20the%20channels.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMaybe%20some%20downtime%20based%20on%20rolling%20out%20new%20features%20for%20Ignite%3F%20Nevertheless%2C%20two%20days%20without%20connectors%20isn't%20building%20trust%20at%20all.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-109814%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20500%20by%20calling%20and%20creating%20a%20webhook%20connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-109814%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20here%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-109742%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20500%20by%20calling%20and%20creating%20a%20webhook%20connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-109742%22%20slang%3D%22en-US%22%3E%3CP%3EYeah%20I%20have%20the%20same%20issue.%3C%2FP%3E%3CP%3Eonly%20new%20webhook's%20fail%20to%20create%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Thomas Goelles
MVP

Since yesterday I get error messages while trying to call a Teams webhook of my channels.

 

"Webhook message delivery failed with error: Microsoft Teams endpoint returned HTTP error 500 with ContextId tcid=105260188274304390,server=EAP010211239200.." Is the answer I get by running my demo scripts that worked now for a few months. I get this now on every webhook I configured at this tenant. All of them worked by Friday but are broken since at least Saturday evening UTC.

 

At first, I thought maybe something gone wrong with that tenant. Today I created a new Team in a different tenant in the web interface. I tried to create a webhook and boom:teamserror.png

 

 

 

So at least 2 tenants with error 500 while dealing with connectors in Teams. Anyone else getting these kinds of errors at the moment?

4 Replies
Highlighted

Yeah I have the same issue.

only new webhook's fail to create

Highlighted
Highlighted

Looks like it's back to normal now.

 

At least my Azure Functions trigger my connectors again and I get the messages in the channels. 

 

Maybe some downtime based on rolling out new features for Ignite? Nevertheless, two days without connectors isn't building trust at all. 

Highlighted

yeah same here, and the newly created webhooks, also work, no need to recreate them.

Related Conversations
MSTeams Groups in outlook with macros disabled
ReadyorNot in Microsoft Teams on
0 Replies
Unknown Login Error
Alex_P3462 in Microsoft Teams on
0 Replies
Spelling Pop-Up Stuck on SharePoint List
aricornish in SharePoint on
0 Replies
Problem with OneDrive
esholder in OneDrive for Business on
5 Replies