Power Platform Community Forum Thread Details

Custom Microsoft Copilot on Teams Crashing with File Uploads, GIFs, and Emojis

Hello,

I’ve set up a custom Microsoft Copilot on a Teams channel, and I’m facing the following issue: Whenever someone uploads a document (e.g., PDF or Word file), sends a GIF, or even uses emojis in a message, the following error message is produced:

Sorry, something unexpected happened. We’re looking into it. Error code: SystemError. Conversation ID: a:1_LhDyUqU9KLZ92bea54o-32YS0392XQNl6GtUgsvyupvnb5H8QWLMhwTJSGZ0wXuqFk2nqKSFgM42ctAMbP2mzlKnTSr56kSgEgs3SfHUQvx5QozC9SX9HmWunHr8jQ9. Time (UTC): 10/21/2024 3:10:51 PM.

For any further messages (not including attachments/GIFs/emojis), the same error message is produced, and is only fixed by removing from the Teams channel and re-publishing. The issue will return whenever another document/GID/emoji is sent.

Here’s a breakdown of the issue:

Normal messages are processed correctly and everything works as expected.
Document uploads (like PDFs, Word files, etc.) seem to trigger the crash.
GIFs and emojis also seem to cause the system to break.

I believe I need to create a custom topic or perhaps some fall-back logic to handle non-text inputs (like attachments or media files), but I’m not sure exactly how to configure this in Copilot Studio.

Has anyone else encountered this issue or found a way to handle non-text inputs effectively within Copilot Studio? Specifically:

How can I prevent the system from breaking when someone uploads files or sends GIFs or emojis?
Is there a way to filter out or manage these inputs gracefully without crashing the system?

Any guidance or suggestions would be greatly appreciated!

Categories:

General

Hi DF-21101516-0,

Yes you can create a custom topic in Copilot Studio that identifies non-text inputs and responds appropriately. This fallback logic helps prevent crashes by catching non-supported inputs before they cause issues. Use conditions to differentiate between text-based inputs and non-text inputs.

For example, if the user sends an attachment or media, you can configure a response like "File uploads are currently not supported."

Use the Power Automate flow to detect non-text input such as file attachments, images, or emojis. I have not tried this, but technically the below should be possible.

Set a trigger for the flow to respond whenever a message is received in the chat. You can use the Microsoft Teams connector with the trigger “When a new message is posted in a channel” or “When a new message is posted to a chat”.
The Microsoft Teams connector allows access to the message body and metadata (like attachment types). You can use the “Attachments” field or message body content to detect these.
Use expressions to check if the content type includes known types such as - .pdf, .docx, .jpeg for files. GIFs can be detected if the message contains media attachments or certain keywords like "gif".
Something like this -> contains(triggerOutputs()?['body/Attachments'], 'gif')
Send a message back to the user saying something like: "The system does not support file uploads or GIFs."

Thanks.

Quick Links

Leaderboard