Answered

Flow automatically stops after processing a certain # of rows of data

(0) Share

Report

Posted on by jessie_0011

Hi Everyone,

My flow processes spreadsheets with hundreds of rows of data. The flow runs a specific loop and is only supposed to exit that loop if it encounters a blank row of data. For some reason, the flow stops after processing exactly 18 rows of data. Does anyone know how to ensure that the flow moves on to the next rows of data and doesn't just stop after doing the first 18?

I've tried adding a counter variable, increasing that variable by 1 every time a row is processed and stating that the bot should only exit the flow if the counter hits a specific number. That didn't work.

Any idea why my flow ceases operations after 18 rows?

Thanks!

Categories:

Power Automate Desktop

I have the same question (0)

All responses (4)

Answers (1)

Sort by

ryule 929 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Have you confirmed it's correctly capturing your full table? Perhaps you hard coded it to 18 by accident?

Was this reply helpful? Yes No
jessie_0011 11 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @ryule, yes, I'm reading all cols up to the first free row. I have another flow that this is happening with too - that one will only read up to 33 rows of data at a time before stopping.

Was this reply helpful? Yes No
ryule 929 Super User 2024 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

It definitely seems odd that they are failing at the exact same place each time. The first free row action is working correctly (capturing the correct row #)? No hidden rows in the workbooks? Can't really think of anything else....I definitely haven't ran across this issue....Is the bot capturing any errors if you throw the Get Last Error action in your bot?

Was this reply helpful? Yes No
Verified answer

jessie_0011 11 on at

Like
a
(1)

Report
Copy link

Link copied!

@ryule , It's actually working correctly now. I needed to set the READ XLS function to "Entire Worksheet" instead of a range of cells. Guess there must have been hidden cells or something...but so odd that it would stop in the exact same place each time. Still can't explain why, because the way that the READ function is setup is the same for several other flows that work perfectly.

Was this reply helpful? Yes No