-
Notifications
You must be signed in to change notification settings - Fork 804
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The bot is not part of the conversation roster. #1470
Comments
@JonoSuave - Thank you for your inquiry about your Teams app development issue! This information will help us better understand the situation and provide a more accurate response. |
Sample Link: Reproduction Steps: Follow the repo's instructions by creating an anonymous access Azure storage blob container. Upload two files, PolicyGuidelineDocument.pdf and ProposalDocument.pdf. Create an Azure OpenAI gpt-35-turbo model to get the END_POINT, API_KEY, and DEPLOYMENT_ID. Populate the variables in the .localConfig. Click the Debug in Teams (Edge) option, add the app, add the Compliance Checker message extension from the compose input of a conversation, and then type in ProposalDocument. @Nivedipa-MSFT one thing I'd like to confirm is whether the Deployment Id is gpt-35-turbo? If not, were do I find the deployment id? |
@JonoSuave - We have tested msgext-ai-doc-compliance-checker sample using Teams Toolkit and encountered the same error. The sample team is investigating it. We will let you know once we have any updates. |
I am encountering the same issue, are there any updates on this? |
I'm trying to serve up the ai-doc-compliance-checker sample, but keep running into the following error when debugging locally:
The bot is not part of the conversation roster.
I've uploaded a ProposalDocument.pdf and PolicyGuidelineDocument.pdf in blob storage and typed in ProposalDocument into the compose msg ext search input. Here's the full error:
The text was updated successfully, but these errors were encountered: