Hi DF-21101516-0, did you ever find a solution to this? I'm running into the same problem. This error would make a custom Copilot unusable in Teams, as one person could disable it until the whole app is manually disconnected and republished. A simple "Thanks 😊" is enough to put the bot into this error loop.
I have tried to create a topic that catches a user message with an Emoji/GIF/file attachment like @Vinoth suggested:
This catches the user message and then displays the "Sorry" message. But still, every user input after that triggers the SystemError and I need to disconnect and reconnect the bot to teams to fix it.
I have tried every variation and combination of ending the topic/conversation and clearing variables after catching the message, but still the problem persists.
Strangely, when you pass the conversation to the "End Conversation" topic, the user can still navigate through the menu, rate the chat and select if the question has been answered. But when another input is made after that, the SystemError will be displayed again.
My last idea would be to somehow delete the Activity.Attachments table before continuing with the topic, but I couldn't find a way to edit the variable.
Does someone know how to fix/prevent this?
Edit: After disabling "orchestration" the error does not occur anymore. So it definitely has something to do with it. Unfortunately, I cannot disable it for my Copilot, as many of its topics use the dynamic filling of input variables. There don't seem to be any further settings for the orchestration feature, so for the time being a functioning workaround would be nice.