Why does Post adaptive card and wait for a response take two minutes to register a response?

[LeongQJ]

Recently, the "Post adaptive card and wait for a response" is taking a lot longer than normal. It used to take only a few seconds, but is now taking almost two minutes, causing Power Virtual Agents to time out. This issue is affecting all of my flows, and the flow fails as the 'Return values to Power Virtual Agents' times out.

I am thinking it might be a rate limit, but I read through the documentations and it appears that most of the time I should be getting an exception if I exceed it, rather than being slowed down. There has only been 400 actions a day (way lower than 10,000 as specified here: https://docs.microsoft.com/en-us/power-automate/limits-and-config)

The weird thing is, if I resubmit the flow via the run history rather than triggering it from Power Virtual Agents, the response is registered in 5 seconds.

[MikeBerendsen]

I'm trying to show Adaptive Cards as being useful in PVA to my manager, and ran into this 😣 Given the comments that Microsoft is working on it for 3 weeks, I wanted to share a work around because I can't wait for Microsoft. 

If you nest your Post Adaptive Card and Await response in another flow triggered by HTTP, 

the submit action is registered by the Adaptive Card wait action and the flow completes as fast as expected. 

You just have to have the HTTP premium connector, and pass any variables in the header or body back and forth like a normal API Post call,

Hope that helps someone while they fix this.

~Mike

[doschtert]

Hi Mike,

I tried your workaround and it did not work from my side. I still get a time out from PVA after a certain amount of time. 

In the PVA Testbot, it works fine, but so does the direct "Adaptive Card and wait for a response" flow. 

Are there special settings you have set in your HTTP requests? 

Thanks! 

[vinod_reddy_257]

It works well in dev environment but creates delay and time out in prod. Any solution please!

[vinod_reddy_257]

It works if you delete PVA Output in the last in power automate flow. Only problem is you the topic with power automate action should be the last

[AC130]

The workaround we had to put in place in our case was to move the "Return value(s) to Power Virtual Agents" step up in the flow to prevent PVA from timing out while waiting for a response. This allows PVA to complete the topic run while still allowing the adaptive card's function to work correctly within the PA flow. It is worth noting that our PVA topic did not depend on the return value to work correctly as PA handled the rest once the card received input from the user that called it, so the return value to PVA was arbitrary.