Hi,
Seeking help with a copilot working in the Copilot Studio environment, but not working when deployed to Teams. We are able to get a couple of conversation flows in, but after that it stops working and we get a system error.
We have the same issue, currently have an active ticket with MS support. Hopefully we can resolve this soon, since it impacts thousands of users in our tenant.
I'm having the same problem too.
I always use the chatbot to get generative answers using a sharepoint link.
I have two chatbot, both of them are correctly responding in the testing environment in copilot studio but they gave me a system error on teams everytime I ask them something. Even if I write "Hello" it gave me this error back:
Sorry, something unexpected happened. We’re looking into it. Error code: SystemError. Conversation ID: a:1SjeyBkKZaslmU3MBidtbsPF8oQ5IIpaBZ9ZBYlitl8Y7mnKj4PoppuZsvsCGITPkQxYtAKQDLM8JmrL6te08ZIrDZuQZnnFLd3Ok1P6DT1Ixpxu4mgwzC5MtqCH-bM4I. Ora (UTC): 5/13/2024 12:11:01 PM.
I'm having this problem now across multiple tenancies, the error appears only to occur when a successful result is being provided by the generate AI answer action when it's connected to an OpenAI on Azure data source.
This does not occur in the testing environment in copilot studio, rather the error only occurs once the copilot is published and added to a user's team environment, and when that user is conversing with the chatbot in teams.
At this stage it's a major BREAKING issue for many of our clients - we will have to revert back to using Power Automate and custom code where it would have been nice if Microsoft released a feature like this that actually works.
Note. I have global admin privileges to deploy this into one of the environments in which we are testing. It doesnt appear to be the issue.
Happy to jump on a call with someone from microsoft if they want to see exactly what is going wrong and provide more details.
Hi there Umianta!
Here are the answers to your questions:
1. Sometimes it fails before the conversation step in the screenshot, but it always fails at that step if not before. Even though the full conversation is much longer with many more topics.
2. Yes, it is always successful in the copilot studio test console, or in the default web app but not in Teams.
3. We are triggering the flow at the beginning of the topic before the issues are caused, not at the stage where the issues are arising.
I require additional details to gain a better understanding of this issue.
Is it consistently failing at that stage of the conversation? Has it been successful in the Copilot Studio test console? Are you triggering the flow at the exact point where it's encountering issues?
If this was helpful:
⭐Please mark it as a solution
⭐Give me a thumbs-up
⭐Connect on LinkedIn
⭐I consistently upload technical videos. If you're interested, please visit and subscribe to my YouTube Channel
⭐Always glad to help, Umesh Khandelwal!