07-22-2019 11:15 PM
07-22-2019 11:15 PM
We just noticed that the incoming webhooks feature broke sometime around 07/23 12:50am UTC. The webhook returns with HTTP 200 OK, and the only error message is a .NET exception message without the stack trace. Is there a schema change recently that is being rolled out?
Oddly, this only affected half of our configured webhooks. Newly created webhooks function normally.
$ httpie --json -v POST $url 'text=This is a test.'
POST <redacted> HTTP/1.1
Accept: application/json, */*
Accept-Encoding: gzip, deflate
"text": "This is a test."
HTTP/1.1 200 OK
Content-Type: text/plain; charset=utf-8
Date: Tue, 23 Jul 2019 05:54:04 GMT
X-MSEdge-Ref: Ref A: 46BA11E2F05D4765AAE6D7854B45323B Ref B: TPE30EDGE0217 Ref C: 2019-07-23T05:54:05Z
System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information
08-11-2019 11:19 PM
we had a seemingly similar issue, maybe what helped us might help you, too :)
(We didn't make any manual changes to our O365, tenant or anything beforehand either)
08-12-2019 03:34 AM
@Ines_Trenz_HIRSCHTEC After digging around it looks like Incoming Webhook (and all apps) are added to the account level O365 blacklist. I logged into the Office admin -> Admin Centers -> Teams -> Teams Apps -> Permission Policies -> Org-wide app settings -> Blocked apps, and click X on the Incoming Webhook. After this I needed to wait ~2-4 hours. It seemed that some channel webhook's were quicker to come back than others.
10-07-2019 02:50 PM
I have checked the Org-wide app settings and there are no blocked apps.
Webhooks were working properly until 10/04/2019 and just noticed that they are not working today 10/07/2019.
The POST request returns 200 OK, but with the following message: System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
10-08-2019 01:53 AM
10-08-2019 05:45 AM
@kains4 Even though no one at our company had made any changes to our O365 Teams settings, I had to go into the O365 Admin, go to Teams Admin Center, click Teams Apps, Permission Policies, Org-Wide App Settings, and unblock the Incoming Webhook. It seems like MS might have rolled out a massive change.
One thing I wish is that I could get an email or subscribe to a feed of any changes both in the future and when they are rolling out. We're building a number of internal apps around Teams and it would be nice to know if MS is making changes that will break our apps. In this case we stopped getting internal notifications and thought everything was fine.
10-08-2019 03:01 PM
I have same problem.
If I sent same HTTP requests to the same Incoming Webhook, some sent successfully and others failed with exceptions.
Teams Connector seems unstable these days. Connector application list from channel menu is not displayed sometimes and Connectors Developer Dashboard is sometimes unavailable.