Answered

Flow Performance

(0) Share

Report

Posted on by Community Power Pla...

I have built a rather simple Flow that calls an API, parses the data and inserts it to the CDS. The API calls return extremely quickly when called via Postman, however, when executing the flow, it is currently taking over 16 hours and it is still running. Is there something I can do to improve this?

Categories:

Dataflows

All responses (3)

Answers (1)

Community Power Pla... on at

Like (0)

Report

Re: Flow Performance

Thanks @PowerBack19. I have adjusted the concurrency settings on my "Apply to Each" components and have executed the flow again...we shall see how much of an improvement this provides.

The last successful run took 1d 13:12:09.
Verified answer

PowerBack19 679 on at

Like (1)

Report

Re: Flow Performance

Do you have any "Apply to Each" actions? If so, you can change the Concurrency to speed up the process. You can find more about Concurrency here: https://powerofpowerplatform.com/degree-of-parallelism-in-power-automate/
v-xida-msft on at

Like (0)

Report

Re: Flow Performance

Hi @Anonymous ,

Could you please share a screenshot about your flow's configuration?

Do you mean that the HTTP Request Call takes over 16 hours without any response?

Further, could your please share a bit more about the API response? It would include large data?

Currently, I could not reproduce your issue on my side, and I think it is not possible within Microsoft Flow. Currently, within Microsoft Flow (Power Automate), there is an known limit with the single outgoing Request -- The maximum value of Request Timeout for synchronous calls is 120 seconds. If you have reached this limits in your flow, you would get a time out error.

Please check the following article for more details about the known limits with the HTTP Request:

https://docs.microsoft.com/en-us/power-automate/limits-and-config#request-limits

Please consider take a try to configure the "Settings" of the "HTTP" action in your flow, then turn on the "Pagination" option, set the Threshold property to 100000 (maximum value), then click "Done", try your flow again, check if the issue is solved.

then check if the issue is solved.

If the issue still exists, please consider submit an assisted support ticket through the following link:

https://flow.microsoft.com/en-us/support/pro

Best regards,