Hi Everyone, When i initially tested out airyte (...
# replication-ask-ai
j
Hi Everyone, When i initially tested out airyte (a good 10 months ago now) i setup a webhook to MS teams for the failure notifications. This worked great, however, when i am now trying to set this up on a production server, i am getting a message saying URL is not valid, its the same webhook url i had previously used so looks like it doesn't like MS Teams any more? i am on version is 50.7 Anyone else got a MS teams webhook working recently?
k
Based on the information provided in the extracts, it seems that there have been instances where users have faced issues with webhook URLs, specifically with Slack, but there's no specific mention of issues with Microsoft Teams webhooks. However, there are a few steps you can take to troubleshoot this issue: 1. Verify the Webhook URL: Ensure that the webhook URL you're using is correct and valid. You can test this by using a tool like curl, as mentioned in the [forum discussion](https://discuss.airbyte.io/t/4295). 2. Check Airbyte Version: The user in the forum discussion mentioned that they were able to successfully test the webhook on Airbyte version 0.40.32. You might want to consider testing on this version or updating to the latest version of Airbyte if you're not already on it. 3. Review Setup Instructions: Go through the [setup instructions](https://docs.airbyte.com/operator-guides/configuring-sync-notifications) for configuring sync notifications again to ensure that you haven't missed any steps. 4. Check for Updates or Changes: If you've recently updated Airbyte or made any changes to your Microsoft Teams settings, these could potentially be causing the issue. If you're still facing issues after trying these steps, I would recommend reaching out to the Airbyte community on their [forum](https://discuss.airbyte.io) or [Slack](https://airbytehq.slack.com) for further assistance.
j
I have read through a few post's now saying that it seems to be broken in 50.7 (apologies for not reading them before starting my own post). Hopefully it will be fixed soon