cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Runner55552
Post Partisan
Post Partisan

Do Until Loop Termination

In a Do Until loop, with a condition (such as a certain variable is greater than 1), at what point does the do Until loop stop?  Does it stop at the beginning of the iteration when the condition is met (and thus does not implement actions below it once the condition is met) or does it see that the condition is met, run the loop once more, and then quit?

1 ACCEPTED SOLUTION

Accepted Solutions
Pstork1
Most Valuable Professional
Most Valuable Professional

In my experience it evaluates the condition at the top of the loop.  So if the condition is true when you enter the loop it will never execute the actions inside the loop.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

View solution in original post

17 REPLIES 17
Pstork1
Most Valuable Professional
Most Valuable Professional

In my experience it evaluates the condition at the top of the loop.  So if the condition is true when you enter the loop it will never execute the actions inside the loop.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
DavidYack
Most Valuable Professional
Most Valuable Professional

It should do the actions once and then move on

 

Do (run the actions) then Until (check the condition)

Thanks for that answer, very helpful. One other question.  Will a Do Until work properly if it is embedded inside an Apply to Each loop?  In my case, I am checking a condition to see if it is true, but I need an apply to each loop for to check each record in a SharePoint list.  I'm not sure if Do Until works properly inside a loop.  See screenshot. "Loop daily list" is an apply to each loop that gets records (items) from a SharePoint list, then uses an item from that list in the do until comparison.  I am trying to get the list loop to exit once the condition is met, to avoid unnecessary repetitions.

 
 

my post below did not seem to keep the screenshot.  Trying again.DoUntilFlow.png

 

From my testing, I have not found a way to exit a loop before all items in the Apply to Each loop are completed. I tried using a Do Until loop with a condition, but as soon as the condition involves multiple items from a SharePoint list, an Apply to Each loop is added, and that loop will not exit until all items have been checked.

My conclusion is that loops which involve checking multiple items in a list or library cannot be exited early based on conditions.  We really need a "break" function.

If anyone has figured out a way to exit a loop (where repeating items are involved), please let the community know.

cerberus
Frequent Visitor

Honestly cannot believe that a "break" hasn't been implemented.

Do until will work fine inside an Apply to Each, but breaking out of the Do Until will just run the next apply to each loop.  There is no way to break out of an apply to each loop without terminating the entire flow.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Which is preposterous.

Pstork1
Most Valuable Professional
Most Valuable Professional

Why is that preposterous?  Its apply to each, not apply to them until I decide differently.  You can easily replace the Apply to each with a do until loop and get the ability to break out of the loop.  Just because doesn't work the way you want it to doesn't make it wrong or preposterous.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Apologies - I shouldn't have said that yesterday. 😔 I find the user interface very frustrating to use and my temper got the better of me.

 

I was concerned that using a do until would be inelegant if the condition is never satisfied but I know that we can limit the number of executions. I will try this.

Anonymous
Not applicable

I have experienced the opposite, where the loop will run regardless of the conditions being met in actions prior.

 

I tested this by setting up a manual flow that has a Do Until loop with the condition to not run if the variable is greater than 0. I initialized the variable at 1 and ran the flow and the action inside the loop still ran. See attached image as evidence. Loop Testing Proof.png

This suggests that Do Until actions check the conditions after their first run, rather than at the start.

 

The easiest way around this would be to put the loop inside a condition matching that stated in the loop conditions. This is a bit redundant but seems necessary.

 

However, this has proven troublesome in some of my more complex flows where I hit the nesting limit when doing this. In response, the solution I have adopted is to utilize run conditions in actions prior to the Do Until loop. For example, by putting that matching condition action before the do until loop and forcing a failure in the "Yes" box the actions below will be skipped. The way I have been forcing a failure is using the expression formatDateTime(null), but any other should do. You would then need to add a parallel branch that runs on action failure. Finally, the action after the scope containing all this would need to run on both success and failure of the scope. See image below.Do Until loop solution.png

 

 

Admittedly, this solution is convoluted, to say the least, and it makes error handling a bit tricky because unless you specifically address it any errors that happen inside this scope would be ignored and the flow would continue. So I am open to hearing any other workarounds that people smarter than myself may have come up with.

The Do Until action always executes the loop at least once, it appears. The Accepted Solution here should be changed.

Do until loop does not stop checking the condition even though the condition is met. It keeps on checking the condition until it runs out of time out or count. It weird that it won't stop once the condition is met. 

 

saishiva_2-1679330117155.png

 

 

saishiva_0-1679330041455.png

 

 

It ran for 5 times within 5 minutes (i kept time-out value of 5min).

 

saishiva_3-1679330313070.pngsaishiva_4-1679330392245.png

 

I have somewhat of a similar issue.

So my flow is meant to delete all duplicate found of a certain value looping through a list; the idea is to check the number of occurrence of the duplicate value (lets say 3 duplicates) and then keep deleting until only 1 is left.

ibi_3_7-1713651763781.png

The number of duplicate if first taken before the "Do Until" step and that is set as a variable input and the value is reduced using the "set decrement" step in the "Do until" step

ibi_3_8-1713652089412.png

 

Initially i kept getting the error so i added a delay in hopes that it reduces the flow cycle speed, sometimes it runs ones and exits the loop with no error as seen in the picture below.

ibi_3_0-1713650486313.png

 

And another time it runs multiple times (sometimes 4 or 6 times) before eventually running into an error

ibi_3_1-1713650636968.png

 

and the error is 

ibi_3_4-1713650803793.png

 

I decided to add an extra check within the "Do Until" step; at first it went well as seen

ibi_3_5-1713651286796.png

 

But on subsequent runs, it fails with attempts as high as 60 cycles with the same error as above

ibi_3_6-1713651414704.png

 

 

Please how can i rectify this error?

Pstork1
Most Valuable Professional
Most Valuable Professional

Please post this as a new question.  You'll get more responses and others will be able to find the answer more easily later.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

"There is no way to break out of an apply to each loop without terminating the entire flow" - 

Terminating the flow is exactly what i want it to do at this stage, how can i implement that?

If you want to Terminate the entire flow you can use the Terminate action inside the apply to each loop for the condition where you want to end the flow. Terminate can be report the flow as Succeeded, Cancelled, or Failed.

image.png



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Results posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (3,632)