I have one flow that currently goes for 8 Hours every day. I runs it from 4pm. I would dearly love it to be less, but it sends a an individual email to our 29 stores with their current list of open orders in an excel spreadsheet.
I need to do this as I cannot put our system onto the Clients network, they are all blocked from office 365 Cloud platforms.
My problem is the flow takes an excel template deletes any rows and then adds rows applicable to the store. It then send s it as an attachment to an email to that store. The process loops ad it does this again. Some larger stores can have over 1000 rows in the spreadsheetEverything was going fine for months, but recently I started getting fails based on the delete row action. The message was that the row ID does not exist. When I look at why, as the ID is unique, I find it did exist but was deleted earlier in the process. Now for some reason it looks for that row again. This is not consistent, it can be the next part of the process or a number of records later.I have found a work around by putting a number iterations based if the action fails. In this particular flow it can fail up to 7 times but I get it to completeI have a number of smaller flows that do something similar in sending spreadsheet orders to suppliers and I am noting thise are starting to show the same problemAny ideas?
For anyone with similar issues...
Seems like there are several good suggestions through the thread for more efficient re-designs of the flow. But if some of those are not possible for any reason, I have a more brute-force solution to all this by just making any Power Automate Excel CRUD operation much faster & more efficent.Excel Batch Upsert: https://powerusers.microsoft.com/t5/Power-Automate-Cookbook/Excel-Batch-Create-Update-and-Upsert/td-p/1624706Excel Batch Delete: https://powerusers.microsoft.com/t5/Power-Automate-Cookbook/Excel-Batch-Delete/m-p/1634375#M735If you're able to pick these up and Create, Update, or Delete 500-1000 rows a minute, then perfecting all the specifics of the use-case may not be necessary.