Adaptive Card can't reach app (sometimes)

[Elias_Gda]

Hello,

in our organization we want to build static adaptive cards to get inputs for a specific problem via Teams. When I say static cards I mean adaptive cards, that stay in the channel when you press the Submit.Action-Button. Behind that we've got another flow that triggers when someone presses the Submit.Action-Button and reads the inputs of the user. They are linked through the "Card Type ID"

While testing our flows we've encountered the problem, that sometimes the user gets following error. Please don't mind the german language. In english the error says "The app cannot be reached. Please try again". Problem is, that this problem doesn't occur like once or twice, but nearly 50% of the time. 

The second problem is that this error message sometimes isn't true at all. Sometimes the user gets the error message, but the second flow triggers and everything works as we wanted. This can be extremely distracting for the user...

To rule out, that the problem comes from the card payload itself, I've created two test flows:

The adaptive card:

{
    "type": "AdaptiveCard",
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "version": "1.4",
    "body": [
        {
            "type": "Container",
            "items": [
                {
                    "type": "TextBlock",
                    "text": "Version: 1.4",
                    "wrap": true
                },
{
                    "type": "Input.Text",
                    "placeholder": "Placeholder text",
                    "isRequired": true,
                    "errorMessage": "Pflichtfeld",
                    "label": "Bitte gib etwas ein",
                    "id": "Eingabe",
                    "value": "Hallo"
                },
                {
                    "type": "ActionSet",
                    "actions": [
                        {
                            "type": "Action.Submit",
                            "title": "Submit the test"
                        }
                    ]
                }
            ]
        }
    ]
}

 I've made over 90 tests with these 2 flows today, where I variated the location (channel or a group), the version of the card (1.1 to 1.4) and even the location where I click the card (Teams in Desktop or web), but wasn't able to find a pattern of when it works and when it doesn't...

Could it have something to do with our vpn or other network settings in Teams/PA that we use at work? Or are these adaptive card just not made for this usage?

Thanks for answers upfront 🙂 If you need any information, I would be happy to help ^^

[ManishSolanki]

Hi @Elias_Gda 

It is mentioned in the troubleshooting link Create flows that post adaptive cards to Microsoft Teams - Power Automate | Microsoft Learn, there are 2 root causes of it:

• Using an action, which does not include ‘wait for response’ in the name

• Attempting to submit the card more than once. Each Adaptive Card can be submitted only once, after which all further submissions will be ignored.

Pls check if you are sending multiple cards at once as per last point. I would recommend you go for "Post an adaptive card and wait for response" action which will wait for the user responses and avoid getting those errors. But changing it would require restructuring the flows actions & connectivity.

If this helps & solves your problem, please remember to give a 👍 and accept my solution as it will help others in the future.

Thanks

[Elias_Gda]

Hello @ManishSolanki 

thanks for your message. I've already found this site you've send me while searching for a reason for the error, but in my opinion the information on that site is not accurate.

We are not trying to use the action "post a card and wait for response", but the action "post card to a chat or channel" since it better fits the functionality we want to implement.

And it is absolutely not true that you can submit a card only once... You can get multiple answers from the same card via the second flow that triggers when someone responds to a card with a specific card ID 

It's mentioned here: Link

Maybe this functionality is just not wanted (yet), but for me it is very weird that it works in 50% of the cases and in the other 50% it doesn't.

[AthenaDepper]

I'm getting the exact same error, even though I am using the wait-for-response option, and I am not submitting the card more than once.

I don't know if you tried this as a test, but I noticed that as long as I don't type in the text field, but instead paste in the response, I do not get that error. Annoying as all get out.

[Elias_Gda]

Hi @AthenaDepper 

I've investigated the problem a little bit further and it seems to be caused by the network connection. Since we root all our network traffic through an IT service provider many requests need more than 150ms (I don't know the exact number) until they make it to our azure.

Problem is: After this specific time the request is declined which is why you get that error. You can propably fix it with a Loop on this azure ressource, but we don't have access for that sadly.

[OkamotoKosuke]

Hi @Elias_Gda 

Thank you for sharing your findings on this issue.

Could you tell me how you solve this problem in the end ?

Best regards.

[Elias_Gda]

Hello @OkamotoKosuke,

we didn't manage to fix the problem. I can recommend you talk with your network admin about that topic, since it's an issue in Azure.