Co Pilot Studio Error

Question

Co Pilot Studio Error

Kumar, Vikash 20

I am getting this error constantly when I am using the co pilot studio agent on teams.

Does anyone have idea what's happening here?

I have uninstalled the agent and installed the agent again also in teams but still same issue.

0 comments

Answer accepted by question author

Teddie-D 19,760 Microsoft External Staff Moderator

Hi @Kumar, Vikash

Since this is a public platform, I’ve moved the error message to a private message to avoid exposing any personal or organizational information. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data.

The SystemError message is a generic Copilot Studio runtime error and can be caused by several factors, including Teams channel configuration issues, connector or authentication problems, publishing inconsistencies, or other runtime errors. Similar reports have shown cases where an agent works correctly in the Copilot Studio test pane but encounters issues when running in Microsoft Teams.

To help narrow this down, could you confirm:

Does the agent work correctly in the Copilot Studio test pane?
Does the error occur for all prompts or only specific prompts?
Did the issue start after a recent publish or configuration change?

In the meantime, I recommend starting a new thread in the Microsoft Power Platform Community Forum, where Copilot Studio developers and community members may be able to share similar experiences or provide additional troubleshooting suggestions. Since this is a user-to-user forum, we do not have access to the internal telemetry or backend logs needed to investigate the Conversation ID further, you may also need to open a Microsoft support case and provide the Conversation ID and timestamp shown in the error message, as these details can help Microsoft Support team investigate the issue more effectively.

Thank you for your understanding.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Kumar, Vikash 20 Reputation points

2026-07-20T13:07:29.9866667+00:00

Hi @Teddie-D

Does the agent work correctly in the Copilot Studio test pane?
Answer: yes, and it is working

Does the error occur for all prompts or only specific prompts?

Answer: yes, this is happening with only one user where any prompts are responded with this error.

Did the issue start after a recent publish or configuration change?

Answer: I have published couple of times (changing Agent instructions). It is working on my end, it's just the one specific user issue.

Thanks,
Teddie-D 19,760 Reputation points Microsoft External Staff Moderator

2026-07-21T04:07:47.3933333+00:00

Hi @Kumar, Vikash

Thank you for the additional details.

Since the agent works correctly in the Copilot Studio test pane and is functioning for other users, the issue does not appear to be related to the agent's configuration or recent publishing changes. The behavior seems to be isolated to the affected user's experience in Microsoft Teams.

As an initial troubleshooting step, please ask the affected user to send "start over" in the conversation and run /debug clearstate to refresh the conversation state. Also confirm whether the same behavior occurs in Teams web and desktop clients.

1 additional answer

Your answer

Kumar, Vikash 20 Reputation points

2026-07-20T13:07:29.9866667+00:00

Hi @Teddie-D

Does the agent work correctly in the Copilot Studio test pane?
Answer: yes, and it is working

Does the error occur for all prompts or only specific prompts?

Answer: yes, this is happening with only one user where any prompts are responded with this error.

Did the issue start after a recent publish or configuration change?

Answer: I have published couple of times (changing Agent instructions). It is working on my end, it's just the one specific user issue.

Thanks,
Teddie-D 19,760 Reputation points Microsoft External Staff Moderator

2026-07-21T04:07:47.3933333+00:00

Hi @Kumar, Vikash

Thank you for the additional details.

Since the agent works correctly in the Copilot Studio test pane and is functioning for other users, the issue does not appear to be related to the agent's configuration or recent publishing changes. The behavior seems to be isolated to the affected user's experience in Microsoft Teams.

As an initial troubleshooting step, please ask the affected user to send "start over" in the conversation and run /debug clearstate to refresh the conversation state. Also confirm whether the same behavior occurs in Teams web and desktop clients.

Answer 1

This usually points to a channel-side agent session problem in Teams, often caused by a stale conversation state or a flow/action mismatch if the agent calls Power Automate.

Since reinstalling the agent in Teams did not help, use this order:

Refresh the flow action in Copilot Studio
- Open the topic that contains the Action node.
- Select the ellipsis (...) on the action node, then select Refresh.
- Verify the input and output parameters in Copilot Studio match the parameters in Power Automate.
- Save and republish the agent.
Check for null or missing inputs
- Compare the values passed from Copilot Studio to the Power Automate flow.
- If any input can be null, add a Message action in the flow to capture and return the input values for debugging.
- Add logic or expressions in the flow to handle null or missing inputs.
Force Teams to start a new conversation
- In the Teams chat with the agent, type start over, goodbye, or another phrase that ends the conversation.
- Start a brand-new chat session.
Clear the Teams conversation state
- In the Teams chat with the agent, enter:
```
     /debug clearstate
```
- This resets the conversation context and forces Teams to reload the agent state.

Why reinstalling did not help: Teams can cache an outdated version of the agent conversation, so uninstalling and reinstalling the app does not always clear the broken session.

If the agent uses flows, the most common root cause is that the flow schema changed and the agent was not refreshed and republished, which causes FlowActionBadRequest or similar runtime failures in Teams.