smba.trafficmanager.net/amer returning 404 when sending Teams message about botframework-services HOT 27 CLOSED

The error code is in the body of the response, which is captured in the Exception or Error object thrown by the SDK. The content will be similar to the one below:

{"error":{"code":"ConversationNotFound","message":"Conversation not found."}}

See for example the Body property of ErrorResponseException: https://github.com/microsoft/botbuilder-dotnet/blob/main/libraries/Microsoft.Bot.Connector/ErrorResponseException.cs

If you provide your bot ID and recent timestamps of instances of this error (within 2 weeks), we can check our logs.

from botframework-services.

I don't have access to the link. Here are some timestamps from the last 24hs in UTC:

2023-3-20T14:34:23.6738341
2023-3-20T14:34:23.8924655
2023-3-20T10:37:46.743094
2023-3-20T10:37:46.9479881
2023-3-19T15:48:23.7102831
2023-3-19T15:48:23.9064328
2023-3-19T15:48:23.7102831
2023-3-20T05:53:52.3286748
2023-3-20T05:53:52.6622061
2023-3-19T19:27:49.4917231
2023-3-19T19:27:49.7409761
2023-3-20T01:13:26.6598817
2023-3-20T01:13:26.3532828
2023-3-20T14:34:23.6738341
2023-3-20T14:34:23.8924655

from botframework-services.

Hi, @martinlarosa this url is the Teams service url where bot sending messages to, is this a transient issue or a persistent issue?

If you have a few particular timestamps of failed requests, i can route this to Teams service team for further investigation.

from botframework-services.

It used to happen sparsely, but now it's happening a lot. Multiple times an hour when I created the ticket, less so now.

2022-11-11 01:56:22.352 UTC
2022-11-11 01:56:34.082 UTC
2022-11-11 02:19:13.028 UTC
2022-11-11 02:34:40.545 UTC

from botframework-services.

Hi! I wanted to know if there's any news on this?

from botframework-services.

Sorry for the delay, @martinlarosa, I've opened a ticket to Teams messaging API team. Will let you know once they get feedback

from botframework-services.

Hi @boydc2014, thank you for opening that ticket. Is that publicly available or something internal?
It's happening a lot and caused us a production issue with a customer last week.

from botframework-services.

The response to the 404 should contain a code that indicates what could not be found. See https://learn.microsoft.com/en-us/microsoftteams/platform/bots/how-to/conversations/conversation-messages?tabs=dotnet#status-codes-from-bot-conversational-apis

For this POST /v3/conversations/{id}/activities endpoint, the usual reason is the referenced conversation ID has been deleted.

from botframework-services.

I don't see this in the logs, the message is being sent through Bot Framework .net sdk.

from botframework-services.

@martinlarosa, It's an internal ticket, they are asking for more information
Can you please share more details like tenant id, request id?
Here is the link:
https://portal.microsofticm.com/imp/v3/incidents/details/353458654/home

from botframework-services.

@martinlarosa is this issue still valid? could you please provide more details for this?

from botframework-services.

Hi, it is still happening, and I'm even getting some 403s

We'll add some more logging to try to find the real error message

from botframework-services.

The response to the 404 should contain a code that indicates what could not be found. See https://learn.microsoft.com/en-us/microsoftteams/platform/bots/how-to/conversations/conversation-messages?tabs=dotnet#status-codes-from-bot-conversational-apis

For this POST /v3/conversations/{id}/activities endpoint, the usual reason is the referenced conversation ID has been deleted.

Regarding that, could it be that the conversation ID expires? We didn't expect that. We are actually caching the conversation ids in one of the features where we send proactive messages so that we don't hit the Graph API if we already have the value

from botframework-services.

@aosolis @luhan2017 would you comment on my previous question?

from botframework-services.

Hey @martinlarosa, to your question -
could it be that the conversation ID expires? We didn't expect that. We are actually caching the conversation ids in one of the features where we send proactive messages so that we don't hit the Graph API if we already have the value
I think most likely the thread was deleted by the user. But to really understand the root cause, I need to check logs.

Do you still hit the same issue? If so, could you share the timestamp in UTC, bot id , tenant id and the error code?

from botframework-services.

Any updates on this, @martinlarosa?

from botframework-services.

Is it really necessary to share the bot id and tenant id in a public channel?

Here's an occurrence that has just happened in UTC:
15/3/2023, 16:09:43.5809337

https://smba.trafficmanager.net/amer/v3/conversations/{someId}/activities/{someId}
Result code: 404
OperationId 71a0c935423f289582c1be0d9be85fc9

from botframework-services.

Hey @martinlarosa , do you have access to the link that @luhan2017 shared? If so, could you share the requested information in the ticket?
https://portal.microsofticm.com/imp/v3/incidents/details/353458654/home

We rely on bot id and tenant id to narrow down to specific requests & cross checks due to the amount of traffic.

With the given information, I searched the send activity requests during the given timestamp, and there are quite a few requests with 404 across different bots :/

If you don't have access to the link, so therefore you cannot share the info.. if you can share multiple time stamps (in UTC), I can check each of the requests and infer the necessary data.

from botframework-services.

@martinlarosa - could you please share you Bot Id and Tenant Id to Microsoft Teams Community Help alias?

from botframework-services.

Done, thank you!

from botframework-services.

@martinlarosa - could you please share Tenant Id as well?

from botframework-services.

I missed your email from last week. I just replied with extra information and new timestamps.

Thank you

from botframework-services.

Any news?

from botframework-services.

@martinlarosa @YunnyChung , could you please follow up through email? I am going to close this ticket because it is not a real ABS issue. Please reopen if needed.

from botframework-services.

Hello guys, I have the same issue.

Do you find a solution?

Our bot receive ConversationNotFound since this weekend whereas user still have the conversation and the user exist in the storage.

When I delete the user, I have "User Not found" (so this is normal).

The bug is ConversationNotFound whereas conversation exists for the user.

from botframework-services.

Hi @Steffi3rd , is the issue still happening to you? Could you share more info for us to troubleshoot?

from botframework-services.

@cts2003258 I found an alternative solution here : OfficeDev/TeamsFx#8759 (comment)

from botframework-services.