[Rendering] When running adaptive cards on Copilot Studio - Keeps retrieving data even though its already submitted

Target Application

Copilot Studio

Application Operating System

Windows

Schema Version

1.5

Problem Description

When asking the bot a question it starts retrieving the information and sends it back. However, it still shows the retrieving message. It seems like it's in a constant loop but I don't know why.

The current setup up is the bot uses knowledge we've provided via documents and internal systems. It then processes this information and then creates a generative answer which doesn't actually answer but is stored as a variable. We then added a adaptive card and added the variables in there.

Hope that makes sense. I provided a screenshot of the flow.

Expected Outcome

What should happen is the bot provides the information and waits for the next query from the user. It shouldn't continue running as a loop.

Actual Outcome

The bot just sticks in a loop with no error message.

Card JSON

{
  "type": "AdaptiveCard",
  "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
  "version": "1.5",
  "body": [
    {
      "type": "TextBlock",
      "text": "${var_Citations}",
      "wrap": true
    },
    {
      "type": "TextBlock",
      "text": "---",
      "wrap": true,
      "spacing": "auto"
    },
    {
      "type": "TextBlock",
      "text": "⚠️ **Warning**: This chatbot's responses are AI-generated, based on available information, and may contain errors or omissions. Please verify with trusted sources before making decisions. Use at your discretion.",
      "wrap": true
    }
  ],
  "actions": [
    {
      "type": "Action.Submit",
      "title": "Dismiss",
      "data": {
        "action": "dismiss"
      }
    }
  ],
  "refresh": {
    "action": {
      "type": "Action.Submit",
      "title": "Refresh",
      "data": {
        "refresh": false
      }
    }
  }
}

Repro Steps

No response

Start with the reported Copilot Studio setup, the Adaptive Card JSON, and the attached screenshots; no repository file or test is identified in the issue. Establish a reproducible loop using the documented schema 1.5 card, then trace whether the renderer or Action.Submit/refresh configuration causes repeated processing; done means the card displays once and waits for the next user query.