Cannot catch MemberNotFoundInConversation error when calling getConversationPagedMembers

[seanhsmith]

Cannot catch MemberNotFoundInConversation error when calling getConversationPagedMembers

[seanhsmith]

Hi @JhontSouth,
We create the instance of ConnectorClient as follows where serviceUrl is the serviceUrl value from the related conversation, nothing fancy:

const credentials = new MicrosoftAppCredentials(
  getEnv('MICROSOFT_APP_ID'),
  getEnv('MICROSOFT_APP_PASSWORD'),
)

return new ConnectorClient(credentials, { baseUri: serviceUrl })

The good news is we have resolved not being able to trap this RestError as it was a deployment issue on our side. Our path forward at this point is removing the conversation records that throw these errors from our system when they occur. This issue can likely be closed until the error is reproducible.

[JhontSouth]

Hi @seanhsmith
We have not been able to replicate the error when getting the list of members of a conversation in different channels.
In our tests, the data extracted from the method getConversationPagedMembers returned the members list without problems.
Could you please tell us which channel you are using and if this error happens after a re-call with continuationToken or randomly?

[seanhsmith]

Hi @JhontSouth, we have also been unsuccessful in reproducing this ourselves as well. We are adding additional logging around this code to try and identify some specific conversations with which this is happening. We also don't know what channels are involved, just the conversation.

I just checked the most recent instances of this error in our logs and it looks like none of them specify a continuationToken but recalls also do not succeed. It's as if the conversation being requested just begins to throw the error. One thing we noticed is documentation around the serviceUrl that suggests that it should be stable but that it could change. If the serviceUrl did change and the old one was still being used for the request, could it possibly result in this error?

I can provide client tenant and conversation ID examples when I have them, provided we can do it in a secure manner, and so long as it's not potentially violating Microsoft Teams TOS.

[JhontSouth]

Hi @seanhsmith,
Thank you very much for your information. We will analyze if the serviceUrl is involved.
We look forward to receiving more details about the error.

[JhontSouth]

Hi @seanhsmith,
We tested changing the ServiceURL value in the middle of the conversation, but it caused a different kind of error (bad syntax - bad format of conversation ID). It seems related to the conversationId format that each channel required.
So, unfortunately, we couldn't reproduce the issue.
Could you share with us the method that you're using to create the ConnectorClient instance?
Additionally, could you provide us a simplified project? To understand the architecture that you're using.