Power Platform Community Forum Thread Details

Hi everyone,

We’re seeing a sudden issue where Adaptive Cards in Copilot Studio agents started failing in Microsoft Teams. This was working earlier and started happening without intentional changes to our card JSON/topic logic.

What’s happening

The agent renders the Adaptive Card (buttons show fine).

Immediately after the card is displayed (or after clicking a button), we see one of these behaviors:
1. The agent triggers a fallback/error message like:
  
  “Sorry, I wasn’t able to process that request. Please try again…”
2. Sometimes it also shows duplicate responses (fallback message + our topic response)
3. In some cases we get:
  
  “Sorry, the bot can’t talk for a while. It’s something the bot’s owner needs to address. Error code: AIModelActionBadRequest.”

This is happening even with a minimal card:

{

"$schema": "https://adaptivecards.io/schemas/adaptive-card.json",

"type": "AdaptiveCard",

"version": "1.5",

"body": [

{ "type": "TextBlock", "text": "Proceed with MFA reset?", "wrap": true }

"actions": [

{ "type": "Action.Submit", "title": "Yes", "data": { "mfaResetChoice": "yes" } },

{ "type": "Action.Submit", "title": "No", "data": { "mfaResetChoice": "no" } }

]

}

Categories:

Calling actions from Copilot Studio

Thanks for raising this.

To help isolate and resolve the issue, could you please check the following:

Payload handling in the topic
Ensure that the submit action data (e.g., mfaResetChoice) is explicitly captured and handled in your topic. In Copilot Studio, this is usually accessed via:
```
turn.activity.value
```
If no topic or condition is matching this payload, the system may trigger fallback.
Generative fallback / orchestration
If generative answers or fallback are enabled, the system may attempt to route the submit action through the AI model, which can result in:
- fallback responses
- duplicate replies
- AIModelActionBadRequest errors
As a test, try disabling generative fallback and verify if the behavior persists.
Adaptive Card schema version
Although version 1.5 is valid, the Microsoft Teams channel may have partial support depending on the client. Please try downgrading to:
```
"version": "1.4"
```
Action structure improvements
Adding an id field to each Action.Submit and/or structuring the payload more explicitly can improve reliability:
```
"data": {
  "action": "mfaReset",
  "choice": "yes"
}
```
Channel isolation test
Please test the same scenario in the Copilot Studio test canvas:
- If it works there but fails in Teams, this indicates a channel-specific issue.
- If it fails in both, the issue is likely within topic configuration or payload handling.
Duplicate trigger check
Review if multiple topics (including fallback or “unknown input” topics) might be getting triggered simultaneously, which can cause duplicate responses.