Unanswered

Do until loop logic

(0) Share

Report

Posted on by FoDelement

435

Hello,

I have a flow that runs a Do until loop. In the loop I have a 10 minute delay, and a get item. (SharePoint list)

I have my Count to 5000 and my Timeout to PT120H.

This will hit 5000 checks in 6 hours.

Do the delays not count towards the checks? If so, how can I change the frequency of how often it checks?

2019-05-14 11_40_05-Jump List for Excel.jpg

Categories:

General topics

I have the same question (0)

All responses (7)

Answers (0)

Brad_Groux 4,556 on at

Like (0)

Report

I'd remove the delay from within the do until and would instead run the flow on a schedule, so you would have more insights into the performance of the Flow.
Also, you are using a Get item with a 10 minute delay after it, which would mean you'd only get six list items per hour. I think you need to rethink you're logic.
As an aside, just make sure you aren't exceeding the SharePoint Connector's 600 API calls every 60 seconds limit.
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

Was this reply helpful? Yes No
ScottShearer 25,270 Most Valuable Professional on at

Like (0)

Report

@FoDelement

You might be better off with a redesign of your Flow. I would suggest having a separate Flow that runs when an item has changed. The Flow will check to see if there is a PO. If not, it will exit. If there is a PO, it will move on. As part of this, you may want to add an additional hidden column that you can set to act as a flag - make it a yes/no/boolean column and have it default to no. Set this column to true/yes when when your Flow runs and a PO exists. Add logic that says if there is a PO and this column is set to true, do nothing.

Let me know if you need an example.

Was this reply helpful? Yes No
FoDelement 435 on at

Like (0)

Report

@Brad_Groux wrote:
I'd remove the delay from within the do until and would instead run the flow on a schedule, so you would have more insights into the performance of the Flow.
Also, you are using a Get item with a 10 minute delay after it, which would mean you'd only get six list items per hour. I think you need to rethink you're logic.
As an aside, just make sure you aren't exceeding the SharePoint Connector's 600 API calls every 60 seconds limit.

The issue is, I can't adjust the trigger. I would have to split the flow until seperate parts if I ran it on a schedule, which I do not want to do.

I don't need the next step to happen instantly, so I am fine getting the item six times per hour. My question is, does the loop check it again after the 10 mintue delay, or does it keep checking it (even while loop 1 is delayed).

If it continues checking, is there a way to adjust the degree of parallelism, of a loop? I would like it to check once every 10 minutes, 5000 times or 120 hours before timing out.

Was this reply helpful? Yes No
Brad_Groux 4,556 on at

Like (0)

Report

As @ScottShearer and I both suggest, you need to rethink your Flow design. I don't personally see how this design will function well if at all.
A delay delays the entire Flow branch it is in. You're using a delay within the "Do until loop," so until that loop step is completed no other parts of the Flow will run, unless you have parallel branches.
If you could provide an expanded screenshot of your Flow and steps, and of any detailed error messages you're receiving we could likely better assist you.
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

Was this reply helpful? Yes No
FoDelement 435 on at

Like (0)

Report

@Brad_Groux , I want the flow to stop at this step, until the user opens the sharepoint list and edits the "PO Number" column.

Was this reply helpful? Yes No
Brad_Groux 4,556 on at

Like (0)

Report

@FoDelement wrote:
@Brad_Groux , I want the flow to stop at this step, until the user opens the sharepoint list and edits the "PO Number" column.
Then you should likely use the When an item is created or modified trigger with a condition to check if PO Number has been updated, there is no reason to use a delay or use a loop. With your current design, you are producing far more complexity and system overhead than is required.
You can "nest" Flows as well, so when one Flow completes, you can trigger another one. See the blog post by @Stephen, How to build nested flows with the HTTP action. It steps you through this process of creating a parent/child relationship between multiple Flows, like so:
The Get started with the request and response components documentation could be helpful as well.
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

Was this reply helpful? Yes No
FoDelement 435 on at

Like (0)

Report

@Brad_Groux

Hmm, okay thanks, I will look into splitting it up. I have two of these loops, so I did not want to split the flow, as I am just concerned about the amount of Flow runs, splitting this up would cause.

Was this reply helpful? Yes No