Answered

Respond to Power Apps or Flow Action

(0) Share

Report

Posted on by DO-21051408-0

I saw a similar question related to longer running flows. In my situation, the flow runs generally between 3-5 seconds. The flow runs successfully, including an email being sent, but then the final "Respond to Power Apps" action intermittently fails with a timeout. It is triggered from a canvass app OnSuccess of a form submission that saves to Dataverse.

Is this a known limitation with the Power Apps response timeout window, and what is the recommended pattern to handle this scenario?

ActionResponseTimedOut. The execution of template action 'Respond_to_a_PowerApp_or_flow' is failed: the client application timed out waiting for a response from service. This means that workflow took longer to respond than the aloted timeout value. The connection maintained between the client application and service will be closed and client application will get an HTTP status code 504 Gateway Timeout.

Categories:

Building Power Apps

I have the same question (0)

All responses (2)

Answers (1)

Sort by

Verified answer

Ram Prakash Duraisamy 5,877 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @DO-21051408-0

Yes, it is an Known limitation, Best practice is using asynchronous flows: trigger the flow without waiting for a response, store results in Dataverse/SharePoint, then refresh or notify users separately from the system

Please mark as answer if my suggestion helps.
Subscribe here for More Useful videos : https://www.youtube.com/@rampprakash3991

Was this reply helpful? Yes No
CU25050647-0 2 on at

Like
a
(0)

Report
Copy link

Link copied!

I loved how you broke down the steps for responding to Power Apps actions! Have you had any real-world applications or case studies that basketball stars highlight these methods effectively?

Was this reply helpful? Yes No