Unanswered

Power App Times Out - Too much data to parse

(0) Share

Report

Posted on by BN09

I'm seeking advice on optimizing a Power Apps flow for updating stock quantities on my ecommerce site. Here's the challenge:

Data Source: I download a tab-delimited file via FTP from my supplier, containing around 350,000 SKUs.
Current Flow:
- Download: Successfully download the file using Power Apps.
- Parse: Attempt to parse the 350,000 SKUs.
- Extract: Retrieve the 250 SKUs relevant to my site.
- Update: Update the stock quantities on my ecommerce site.
Issue: The flow times out during parsing, making it inefficient.

I need guidance on architecting this solution more effectively. How can I efficiently process such a large file and update only the relevant SKUs on my site without timing out? Any insights or recommended practices would be greatly appreciated.

Thanks in advance!

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Pstork1 69,653 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

My primary suggestion would be to not trigger the flow from Power Apps. If you trigger the flow using a manual button or a recurrence trigger in Power Automate the flow can run for days without timing out. Is there a particular reason you need to trigger it from Power Apps?

Was this reply helpful? Yes No
BN09 6 on at

Like
a
(0)

Report
Copy link

Link copied!

I intend to trigger the flow on a schedule (2 AM once a day). When I test the flow by triggering it manually, it really chugs parsing the tab delimited file and then doing a look-up against the SKUs. My thought, based on little experience, is to parse the file and store it in a spreadsheet first then do the SKU lookup. Another thought is to only parse the SKUs I need from the text file. So, I would first grab the SKUs from my ecommerce site and then use those to only parse the SKUs from the FTP file. Not sure if this is possible.

Was this reply helpful? Yes No
Pstork1 69,653 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

You won't get the timeout issue if you start it at 2:00 AM using a recurrence trigger. The problem is that Power Apps expects a response from the flow within a couple minutes. That is why its timing out. Its a Power Apps issue, not a Power Automate issue. I would switch the trigger first, then we can try to help improve the performance. But I don't think you will ever get it to run fast enough to trigger in Power Apps.

Was this reply helpful? Yes No