Issue with New Webhooks Returning HTTP 410 Error

[Navega]

Type of issue

Feature doesn't work (bug)

Feedback

We have encountered an issue with our Microsoft 365 connector that has been operational for several years. Recently, we observed that new webhooks created in the past few weeks are not functioning as expected.

Issue Description:

1. Existing Webhooks: Webhooks that were created a few months ago continue to work without any issues.
2. New Webhooks: Any new webhooks we create return an HTTP 410 Error when we attempt to post a card. It is important to note that the same card works perfectly with the older webhooks.

Steps Followed:

We have strictly adhered to the instructions provided in the Microsoft documentation for creating connectors:
Creating and Connecting Webhooks.

Technical Details:

• Our Teams SDK is updated to the latest version available.
• The HTTP 410 Error occurs exclusively with new webhooks, while existing ones continue to function normally.

Request for Assistance:

We request your assistance in diagnosing and resolving this issue. We would appreciate guidance on any changes that might have been introduced recently which could affect the functionality of newly created webhooks.

Please let us know if any additional information is required from our end.

Thank you for your support.

Page URL

https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/connectors-creating

Content source URL

https://github.com/MicrosoftDocs/msteams-docs/blob/main/msteams-platform/webhooks-and-connectors/how-to/connectors-creating.md

Author

@laujan

Document Id

57e368e2-aaed-fa8d-ed49-cc18e594ab1d

[microsoft-github-policy-service]

Hi Navega! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies.

Best regards, Teams Platform

[Nivedipa-MSFT]

@Navega - Thanks for reporting your issue. We have tested this at our end but it's working. Could you please share your tenant id and log details to create an ICM?

[Navega]

Thank you for your prompt response.

Please find the requested details below:

• Tenant ID: df1a799e-f5bd-46c1-abff-df89a1246336
• And our Teams integration where you can reproduce the problem is "Priority Matrix": https://sync.appfluence.com/accounts/get_teams/

We can provide:

Example of Webhook Url: https://appfluence.webhook.office.com/webhookb2/7ec06567-6ccb-4459-8467-c5382d45778b@df1a799e-f5bd-46c1-abff-df89a1246336/80051254-9836-4247-8ce8-7b347eb0da54/4204f01161cc47fb82b085335d58c57d/d2c07276-3f65-4fc8-bd7a-f16e2ceeb45d

Error Response when a card is sent to that URL: _[410]: Connector configuration not found

SDK Logs: Teams SDK doesn't show any console error and this is an example of code where we save the connector config:

const settings = {
        entityId: connector.id.toString(),  // ramdon identifier and unique
        configName: "test name",
        contentUrl: "https://sync.appfluence.com/office365/teams/index/connector",
        removeUrl: "https://sync.appfluence.com/office365/teams/index/connector",
}
microsoftTeams.pages.config.setConfig(settings)

and previously we got the webhook url from:

microsoftTeams.pages.getConfig().then(async settings => {
        const webHook = settings.webhookUrl
        // extra code
        }

I think the problem could related to "setConfig" and webhook not being created, but I don't know how to validate it.

We appreciate your assistance in resolving this issue. Please let us know if any additional information is needed.

[Nivedipa-MSFT]

@Navega - We have already raised an ICM for this. We will inform you in this thread once we get any updates. Thanks.

[EamonnHegarty]

Following, as have similar problems with existing webhooks recently stopped working.

[Navega]

@Navega - We have already raised an ICM for this. We will inform you in this thread once we get any updates. Thanks.

Hello @Nivedipa-MSFT, any update here?