Forum Discussion
Webhook connector returns 500 error from AWS Lamda
Over the past few months we've had multiple webhooks configured that gives us daily reports on things like metrics and API availability, these reports are generated by an AWS Lambda function and since the 5th of July the webook stopped working.
In our AWS account we can see the lambda are triggered, but the HTTP request is returning an 500 error. We do see the following error logging:
When I copy the URL and the body into postman it does not give the 500 error and the message is also visible in teams.
Because its a 500 I would think it has to do with something from the Microsoft side, but it works locally... The only difference is that the webhook goes to an Dublin server, and locally to Amsterdam.
any ideas?
2 Replies
- I have the same problem since July. Anyone from Microsoft side can help on this?
Just update for someone finds this.
It turns out that we didn't assign the `content-type=application/json` and it was working for a while but since July 6ish there must be some changes on MS Teams side to enforce the checking.
