Power Platform Community Forum Thread Details

"Hello,

I've several flows that execute a stored procedure in a SQL Server and return the rows back to the caller of the flow, in his case a PowerApp.

They have been failing sporadically with a TimeoutError on the response action. Multiple of these flows are called at the same time during a single load of my Powerapp. I've noticed that the failure seems to affect all executed flows at the same time.

I can't find a way to increase the timeout on the response action. It is also confusing that it is timing out with such a short execution time (0s), especially when some of the other runs that do not fail show the exact same execution time on this action.

the full error text reads "Action 'Response' failed: The execution of template action 'Response' is failed: the client application timed out waiting for a response from service. This means that workflow took longer to respond than the alloted 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:

Using flows

Hey @DL-28071629-0

Thanks for the detailed explanation.

One potential factor I’d like to explore is licensing: since your flows use the SQL Server connector, which is classified as a Premium connector, each end user who triggers these flows through the PowerApp must also have a Power Apps Premium license (Per User or Per App plan).
Could you please confirm whether the end users encountering these issues are licensed accordingly?
If the licensing is all in place and valid, another thing to consider is whether the SQL execution logic could be handled directly within the app — either using a collection or PowerFX-based filtering (if the dataset size allows) — rather than calling a Flow for each load. In some cases, consolidating logic within the app helps avoid the performance hit and network latency caused by multiple simultaneous HTTP requests.
Let me know what your current licensing setup looks like, and if needed, I’d be happy to work with you on alternative approaches that might help simplify the architecture and improve reliability.

Best regards,

Sam