'something unexpected happened' Error since a publish

(0) Share

Report

Posted on by GD-02051104-0

Hello,

I have created an agent which was published to Teams (FYI I have to Submit for admin Approval before seeing it there). Initially the agent was working well but there were some UX issues when triggering flows/ topics so I fixed them, they work great in the test pane. I re-submitted for approval (along with requesting for it to be published with a fellow employee), it was published again, however now in Teams every time I send a message (Even if I simply say "Hello") I get the response:

Sorry, something unexpected happened. We're looking into it, Error code: SystemError. Conversation ID: *** Time (UTC): ***

I mentioned this to our admin who is approving the publishing but she claims to have done nothing different. Only thing she noticed is that there was also a second 'Scout' agent for approval which when clicked on had the exact same name, icon description etc. as this agent. We therefore rejected that one and deleted the publishing of my agent, hoping to 'reset' the situation.

I submitted the agent again for approval, only the agent showed (no 'Scout') so this was published. However I still I get the error whenever I send a message. All of my other agents are working fine.

Categories:

Building Copilot Studio chatbots in Microsoft Teams

I have the same question (0)

All responses (9)

Answers (0)

Sort by

MichaelFP 2,001 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!

First thing try to execute the command /debug clearstate, after that check if stop to see this error.

If not check using teams web, using de developer toolbar if shows any errors in network tab, usually show the error we you can work on a fix for that.

Are you all the time create a new agent in dev.teams.microsoft.com or you just update the version?

-----------------------------
If my answer helped you, please give me a thumbs up (👍).
If solve your question please mark as answer ✔️. This is help the community.
If you want talk with me just tag me @MichaelFP

Was this reply helpful? Yes No
GD-02051104-0 23 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello @MichaelFP,

So I executed the command /debug clearstate and it says Conversation ID cleared successfully but then when I type another message it just goes back to the same error.

In the developer toolbar it says:
{
"errorCode": 404,
"message": "Conversation was not found",
"subErrorCode": "RequestHandlerException"
}

Was this reply helpful? Yes No
Suggested answer

deepakmehta13a 369 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi,

Since:

It was working before republish

You are using admin approval flow

A duplicate agent (“Scout”) appeared and was rejected

Now only this agent is broken (others work fine)

This is very likely not a flow/topic issue, but a broken Teams ↔ Copilot Studio binding after approval/publish.

What’s happening most likely:
Teams is still trying to use an old or invalid conversation endpoint (conversationId) that no longer exists after the re-publish, especially because the approval pipeline briefly created duplicate app registrations.

What you should try

Full cleanup

Ask your admin to

Remove the agent completely from approved/published apps

Check if any duplicate or older versions still exist and remove them

Republish as a fresh version

Make a small change (e.g., description/name)

Submit again for approval

This helps generate a new app package instead of reusing cached one

Reinstall in Teams

Uninstall the agent from Teams

Sign out/in (or try Teams web)

Add the agent again after approval

Test with another user

If it works → confirms user session/cache issue

If not → confirms publish binding issue

Why /debug clearstate didn’t fix it

That command clears the client conversation state, but your issue is server-side mapping (conversation not found), so it keeps failing with the same 404.

If this still doesn’t resolve after a clean re-publish, it would likely need Microsoft support to reset the backend registration.

-------------------------------------------------------------------------------------------------------------------------------------------

Hope this helps.

If this helps resolve your issue, please consider marking the response as Verified so it can help others facing a similar scenario.

If you found this helpful, you can also click “Yes” on “Was this reply helpful?” or give it a Like.

Was this reply helpful? Yes No
Suggested answer

MichaelFP 2,001 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!

@GD-02051104-0 after do it the /debug clearstate, remove the agent from teams and include again. Test that, because now you don't have the conversation linked to the old teams app.

Once you publish in teams you don't need to update the teams app all the time.

-----------------------------
If my answer helped you, please give me a thumbs up (👍).
If solve your question please mark as answer ✔️. This is help the community.
If you want talk with me just tag me @MichaelFP

Was this reply helpful? Yes No
GD-02051104-0 23 on at

Like
a
(1)

Report
Copy link

Link copied!
@MichaelFP

I did these steps and still get the error:

Did the /debug clearstate and sent no other messages after receiving confirmation it was successful,

Admin removed the agent from teams

I made a small change in the instructions and published from there

Then submitted for admin approval

The agent was approved

I sent a message saying 'Hello' and nothing changed there. I still go the error.

In terms of going forward now I guess I have two options?:

Ask my colleague to try the agent from their teams (they are on annual leave so have not even added the agent once yet)

Rebuild the agent (copying everything from the original) and trying it fresh/

Unless you can think of anything I have missed?

Was this reply helpful? Yes No
MichaelFP 2,001 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!

@GD-02051104-0

Ask to you colleague to test, if not work create a new teams app from scratch an check if the error occours

-----------------------------
If my answer helped you, please give me a thumbs up (👍).
If solve your question please mark as answer ✔️. This is help the community.
If you want talk with me just tag me @MichaelFP

Was this reply helpful? Yes No
GD-02051104-0 23 on at

Like
a
(1)

Report
Copy link

Link copied!

@MichaelFP

I had some interesting/frustrating development on this. I had to recreate the agent as no matter what I did I couldn't get a response from the agent. So I made a blank agent and copied the instructions, sub agents and knowledge across. As well as re-mapped a flow and prompts.

The new agent was published and approved on Thursday 2nd April 2026 and I have been using it absolutely fine for the last week. I asked a question this morning at 8:08am and had no issues got the result I was expecting. Then at 11:05am a few hours later asked another question and I got the system error again for the first time. I am now wondering if it is something in the agent that is causing this. In terms of its function it has 3 main functions, 2 of which are extracting data from PDFs through sub-agents and gen AI (no tool). The third is to trigger a flow to create an excel document based of some results of a prompt with the user input as a variable. This just so happened to be the last 'working' response as well (Even though I got another 4 or 5 of these last week).

Here I have provided some pictures with a tick representing the last couple of working messages and then another image with an 'X' showing the first error again when asking to extract some information (this was also working fine last week).

Was this reply helpful? Yes No
MichaelFP 2,001 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Thanks for de details.

I would recommend to update the OnError Topic to show the details, could be a token limit issue.

Inside the On Error topic in all agents related, copy the message below the test mode validation, to the All other conditions. In that case it will show to you the correct message that happen.

after done that paste the error here to help

Was this reply helpful? Yes No
GD-02051104-0 23 on at

Like
a
(1)

Report
Copy link

Link copied!

@MichaelFP Sorry for the long reply on this.

I added the message part to the on Error topic and when pressing publish this didnt update in teams so I had to submit fr admin approval again, which took a while for approval.

Once it came I tested the agent to get the error again and now the agent has started working no problem, I am going to extensively test this over the next few days but really strange it now works fine. If I get the issue again I will provide what the message says next time.

Was this reply helpful? Yes No