Information message does not clear when adaptive card is updated

Question

Information message does not clear when adaptive card is updated

Boris Rusinovic 96

Here is the scenario:

On Action.Execute Teams sends an "invoke" request to the bot.
Bot replies with the information message, something like "Please wait! System is processing your request."
On the second thread, the bot processes the request and sends the message update (adaptive card) to Teams
Teams app updates the adaptive card in the chat, but the information message (from step 2) is not cleared
A user has the feeling that nothing happened because the information message "Please wait..." is still there

This problem is happening only in the Teams app and the browser on the desktop. Mobile Teams apps on Android and IOS clears the information message on adaptive card update.

Is there a way to explicitly clear the information message with the message update on conversation/activity?

Is this a bug?

ref: https://learn.microsoft.com/en-us/adaptive-cards/authoring-cards/universal-action-model#response-format

Thanks

Boris

Capture Step2

Step4

JimmyYang-MSFT 58,781 Reputation points Moderator

2024-02-14T07:44:57+00:00

Hi @Boris Rusinovic Teams tag is mainly focused on the general issue of Microsoft Teams troubleshooting. According to your description, your question is not in our support scope. So I will remove teams tag from your thread. Thanks for your understanding!
Vaibhav-MSFT 15 Reputation points Microsoft External Staff

2024-02-29T09:09:42.0166667+00:00

Hello @Boris Rusinovic ,
To explicitly clear the information message when updating an adaptive card in a Teams conversation, you can utilize the message edit mechanism provided by Teams. By triggering a message edit after updating the adaptive card, you can ensure that the information message is cleared.
Refer this documentation-
https://learn.microsoft.com/en-us/microsoftteams/platform/bots/how-to/update-and-delete-bot-messages?tabs=dotnet#update-cards
Boris Rusinovic 96 Reputation points

2024-03-13T16:26:02.63+00:00
Hello @Vaibhav-MSFT

I appreciate your response, but this is exactly what my code is doing when updating existing adaptive card:

PUT /v3/conversations/{conversationId}/activities/{activityId}

To further clarify the case:

Step 2: Bot replies with the information message, something like "Please wait! System is processing your request.". Bot returns HTTP OK with the body:

{ "statusCode" : 200, "type": "application/vnd.microsoft.activity.message", "value": "Please wait! System is processing your request." }

Step 3: On the second thread bot invokes the app business logic and, once done, updates the adaptive card using:

PUT /v3/conversations/{conversationId}/activities/{activityId}

As I wrote in my initial question: everything works as expected on Teams mobile app (Android and iPhone), but not on the web and Teams app on Windows or Mac.

Is there anything else that is not mentioned in the documentation.

Please note, our bot is using bot framework REST API and not SDK.

Thanks,

Boris
Vaibhav-MSFT 15 Reputation points Microsoft External Staff

2024-04-05T13:30:22.3433333+00:00

Hello Boris Rusinovic,
Sorry for the delay in response,
Can you please share the card json and deployed manifest file so we can also test this from our end?
Boris Rusinovic 96 Reputation points

2024-04-07T09:52:30.47+00:00

Hi Vaibhav-MSFT,

Since the Q&A does not permit the upload of certain file types:

Bot package: Costpoint Bot.log -> rename to .zip

Sample card: tmpcard.log -> rename to .json

If this does not work, please let me know of other means to send you the file. We can also set up a meeting at your convenience if you need more info. I would appreciate a notice when you will do the testing as the bot is on our dev server and it might not be up all the time. Also, I am not sure if this is going to work as we have tight security checks for requests coming to the bot.

Thanks,

Boris
Boris Rusinovic 96 Reputation points

2024-04-11T19:00:59.2966667+00:00

Hi Vaibhav-MSFT,

I just noticed that the issue appears to be fixed in the New Teams and Teams web app.

Still experiencing the same issue with the old Teams app. Since our bot will be used by many clients with different MS Teams configurations, a consistent experience is of the highest importance. Anyway, this is great news, and thank you.

Regards,

Boris