Adaptive Card Prompt appears again after user switches to another Copilot topic

(0) Share

Report

Posted on by TW-28081114-0

Issue Description

We are using Microsoft Copilot Studio with an AdaptiveCardPrompt to collect callback date and time from users.

The issue occurs when the user does not complete the Adaptive Card and starts another conversation flow.

Steps to reproduce:

User enters the enquiry topic.

Copilot displays an Adaptive Card containing:
- Callback Date (Input.Date)
- Callback Time (Input.Time)

User does not submit the card.

User types another message that triggers a different topic.

The new topic is triggered successfully.

After the topic switch, the previous Adaptive Card appears again automatically.

The user should continue with the newly triggered topic, but the previous Adaptive Card prompt is displayed again.

Categories:

Bot extensibility

All responses (4)

Answers (1)

Sort by

Suggested answer

Mohsin Ali 1,075 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello @TW-28081114-0 - The behavior you're experiencing is in fact an expected behavior, you can refer to following documentation to understand how to handle topic switching while agent is waiting for adaptive card response.

https://learn.microsoft.com/en-us/microsoft-copilot-studio/authoring-ask-with-adaptive-card?#other-properties

Now what you can do is to turn of the interruptions on Adaptive Card node so that if user opt to switch the topic, agent stop waiting response for the adaptive card. You can find the settings Adaptive Card Node -> Properties -> Interruptions

However, if the callback date/time is mandatory, you can disable Allow Switching to another topic, which prevents another topic from interrupting the card. Alternatively, you can restrict interruptions to only selected topics.
Mohsin Ali 1,075 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello @TW-28081114-0 - Just wanted to follow-up if the suggestions shared above really help to sort out the issue or pointed in right direction.
Verified answer

Sayali-MSFT Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hello @TW-28081114-0 ,

This looks like expected interruption/resume behavior of an Adaptive Card prompt. Since Allow switching to another topic is enabled, Copilot Studio can switch to the new topic, but the original Adaptive Card remains pending because the user never submitted it. When the new topic finishes, the previous topic resumes and the card can appear again.

If switching topics should completely abandon the callback request, the original flow needs to be explicitly ended/cancelled rather than temporarily interrupted. Alternatively, disable Allow switching to another topic if users must complete the card before moving elsewhere.
Also, Microsoft recommends using unique data in Adaptive Card submit actions when multiple interactive cards may remain in the conversation.
So this doesn't appear to be an issue with Input.Date or Input.Time. The key point is that the unfinished AdaptiveCardPrompt remains active and is resumed after the topic switch.
Reference Document:
1. Ask with Adaptive Cards - Microsoft Copilot Studio | Microsoft Learn
2. Additional settings for inputs of topics and tools - Microsoft Copilot Studio | Microsoft Learn
3. Adaptive Cards overview - Microsoft Copilot Studio | Microsoft Learn
Suggested answer

sannavajjala87 1,113 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi,

This behavior is typically related to how AdaptiveCardPrompt manages conversation state. Even when "Allow switching to another topic" is enabled, the adaptive card remains an active prompt until it's either submitted, canceled, or otherwise resolved. When the new topic finishes, Copilot Studio returns to the previous unfinished prompt, which is why the card reappears.

A few things you can try:

Before switching topics, explicitly cancel or clear the pending adaptive card state if your design allows it.

Consider adding logic to detect topic changes and skip the callback flow when the user has moved on to a different intent.

If the callback card is optional, you could store a flag indicating the user abandoned the prompt and prevent it from being shown again.

Test the same scenario with a standard question node. If the behavior is identical, it's likely expected prompt-resume behavior rather than an Adaptive Card issue specifically.

Based on your screenshots, this looks less like a topic routing problem and more like the adaptive card remaining in a waiting state. Once the newly triggered topic ends, Copilot Studio resumes the unfinished prompt and redisplays the card.

I'd be interested to know whether you're seeing this in both Test Chat and published channels, as that would help determine whether this is expected runtime behavior or a platform-specific issue.

Thanks & Regards,

Manoj Annavajjala

www.powerplatformengineer.com