Attachments fail with Sorry, something unexpected happened.

(1) Share

Report

Posted on by Shaun arinex

I've created an agent in Copilot Studio that accepts a file, stores it temporarily in Sharepoint, for later processing.

When I test it in Copilot Studio it works like a charm, but when I install the agent in Teams or Copilot, it throws an error when I select a file to attach and hit the send button:

"Sorry, something unexpected happened. We’re looking into it. Error code: SystemError. Conversation ID: 03f6c447-c1d5-4977-918e-3e523fec7f85. Time (UTC): 8/15/2025 3:19:10 AM."

I'm running this as an admin, and I got prompted to Allow sharepoint the first time I tried, so permissions should be fine.

I checked the Activity on the topic flow and the agent, but it hasn't even registered the error, so it doesn't seem to be hitting the Sharepoint flow at all.

Any idea how to go about troubleshooting this?

Categories:

Bot Framework

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Romain The Low-Code... 487 on at

Like (0)

Report

Attachments fail with Sorry, something unexpected happened.

hello, hope you will find the answer, since i had the problem and solve it :)

solution 1 :

In teams : if you send without text a file, copilot studio will trigger the "conversationnal boosting" topic, wich consider empty you'r message and a lot of thing will start to go wrong from here.

So i add a "if then else" when text is empty, i check the attachment content.

Solution 2 :

Could you show you'r code ? recently the properties used to get attachment have stop to accept deprecated code (many people use it since it was a lot show in youtube), you have to use the "new" code with Activity.attachments (and not the one with originalattachements)

I hope this help :)

Was this reply helpful? Yes No
Shaun arinex 6 on at

Like (0)

Report

Attachments fail with Sorry, something unexpected happened.

The plot thickens...

It works fine when I install the agent as an app and tun it from the left sidebar in teams. If I open it in Teams Copilot and use it from the list of agents, I get the "Sorry, something unexpected happened. We’re looking into it. Error code: SystemError"

Also it only seems to work when I upload a document from my device. Selecting a document from recent just makes it reprompt for the attachment.

Was this reply helpful? Yes No
Shaun arinex 6 on at

Like (0)

Report

Attachments fail with Sorry, something unexpected happened.

Thanks for the reply.

So I've checked all the permissions and uninstalled/reinstalled the app, and got a bit further.

I'm still getting the error, but my flow is running all the way through now, so I get the email with attachment that I was looking for.

The user still sees an error though, and the confirmation message in chat doesn't fire.

I've tried adding a "Respond to the Agent" activity to the end of my flow, thinking that maybe it expects an output, but that didn't help.

Edit: Just tried removing my confirmation message and it works!

Was this reply helpful? Yes No
Suggested answer

CU15080535-4 2 on at

Like (0)

Report
Attachments fail with Sorry, something unexpected happened.

I had a similar issue. In Teams, the file upload never reaches the bot because Teams uses a different process than Copilot Studio’s test pane. The Teams app must explicitly allow file uploads (supportsFiles: true in the app manifest) and the tenant policy must permit them. If that’s not set, Teams blocks the upload before your flow runs, causing the SystemError.

Solution

In Teams Admin Center → Teams apps → Manage apps, make sure your bot’s app is allowed and file uploads are enabled in your policy

If you use a custom Teams app package, edit the manifest.json and add: "supportsFiles": true

Re-upload the updated app package to Teams.

Test again — the file should now reach your bot/flow instead of failing with SystemError.

All the best.

Was this reply helpful? Yes No
Michael E. Gernaey 47,123 Super User 2025 Season 2 on at

Like (0)

Report

Attachments fail with Sorry, something unexpected happened.

Hi @Shaun arinex

Depending on the Tool, the connection, the reference it could be any or all of those.

Just to validate, can you please go to powerautomate.com

log in

pick the right environment

Click ... More

select connections

See if you have any that are broken and fix them and try again.

Also, even though you are admin, it also depends on if you have the app enabled in Teams and everything license wise configured properly.

If it fails immediately on just selecting the file and clicking upload/attach, can I ask what triggers that?

Do you have a File Upload Question?

Was this reply helpful? Yes No