Update an Adaptive Card Losing Card Type ID

Question

I have 2 PowerAutomate Workflows sending an adaptive card to Team Group Chat.

First is adding in teams an adaptive card with "Post card in a chat or channel" with the property Card Type ID, within this card there is a multiple-choice selection. There is then a 3 day delay. If there is no response, in the same flow I have an "Update Adaptive Card" action to refresh the card and remind the GC that a response is pending.

Workflow no 2 is using "When someone responds to an adaptive card" with the property card type id configured. As long as I don't update the adaptive card the action.summit works correctly, but if updated I get the error: Unable to reach app. Please try again.

I think once the Update Card action occurs the Card Type ID is wiped and is unable to be received by the second flow. Is there a work around for this?

Answer 1

Dear @Maddie Schlader,  

Welcome to the Q&A Community.    

I understand how inconvenient it can be when an Adaptive Card works correctly at first but stops functioning after it is updated, especially when the update causes the Card Type ID to be lost and prevents the second workflow from receiving the submission. 

Since my current category primarily focuses on Microsoft 365 products, and your concern relates to Microsoft Power Apps, I want to ensure you receive the most accurate and effective assistance. For this reason, I recommend posting your question in the Microsoft Power Platform Community Forum. In this forum, you'll get the most qualified group of respondents, and other partners who read the forums regularly can share their knowledge or learn from your interaction.    

I apologize for redirecting you to a different community, as the members of this category focus on Microsoft 365 concerns and have limited knowledge about Power Apps. To help you get quicker and better assistance, I am guiding you to the appropriate resource.  

As community moderators, we kindly ask for your understanding that our access to internal development details is limited. Our primary role is to guide users toward the appropriate resources and support channels. While we may not have visibility into performing deeper backend analysis, we’ll continue doing our best to support you within the scope of our responsibilities.     

Thank you once again for your precious time and engagement.  

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have any extra questions about this answer, please click "Comment".  

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

Answer 2

When you update an adaptive card using the "Update Adaptive Card" action, it can indeed cause issues with the card's original message ID, which is necessary for the "When someone responds to an adaptive card" trigger to function correctly. This is likely why you're encountering the error "Unable to reach app. Please try again."

One workaround could be to ensure that you are using the wait for a response actions when creating your adaptive cards. This allows the card to handle responses correctly without losing the necessary context. However, keep in mind that adaptive cards created using the wait for a response actions can only be submitted once per card, which means that if you update the card after a response is received, it may not function as expected.

Additionally, consider implementing a mechanism to track the state of responses externally (e.g., in a database or a SharePoint list) so that even if the card is updated, you can still manage and track responses without relying solely on the card's message ID.

If these approaches do not resolve the issue, you may need to explore alternative designs for your workflows that do not rely on updating the adaptive card after it has been sent.