web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Flow stuck in a loop a...
Power Automate
Unanswered

Flow stuck in a loop and can't figure it out

(0) ShareShare
ReportReport
Posted on by 2
Hello,
 
I've developed a flow for a submitting payments to individuals for my job. It is my first experience using the child/parent flow. Everything works fine until condition 8 where it just shoots approvals back forth between two approvers when it is supposed to be just one linear approval from one to the other and then move on with the flow. I've used all sorts of AI help and reached out to those I know who use PowerAutomate but nobody seems to know how to solve it. I've put screenshots below of this area of the flow and what it looks like when it's running and looping in these same spots. Any help would be so appreciated. 
 
Thank you!
 
 
Categories:
I have the same question (0)
  • David_MA Profile Picture
    15,099 Super User 2026 Season 1 on at
    Unfortunately, the screen shots are not very helpful because they do not show the logic of your conditions and you've not explained the logic of all your conditions within your post. However, it seems from what you've stated, that the issue lies within condition 8:
     
    "Everything works fine until condition 8 where it just shoots approvals back forth between two approvers when it is supposed to be just one linear approval from one to the other and then move on with the flow."
     
    Please explain what condition 8 is checking for and how it is configured. Also, what is the trigger for the main workflow. You may have created an infinite loop if you used the trigger when an item or file is modified.
     
    It is also a best practice to give actions meaningful names. Instead of using names such as Condition 8, a name like Condition - Budget Over $1 Million immediately tells you what the condition is evaluating. You'll appreciate that clarity when you need to troubleshoot or update the flow a year from now. The same applies to triggers and actions. For example, instead of leaving the trigger as Manually trigger a flow, consider something like Manually trigger a flow - Finance Approval.

    Personally, I prefer to keep the original action name and add a descriptive label rather than completely replacing the original name. For example, Condition - Budget Over $1 Million or Send an email (V2) - Notify Requestor. This preserves the action type while making the purpose of the step obvious at a glance.
  • CO-15070038-0 Profile Picture
    2 on at
    So I've tried the renaming and I'm not sure if it's because of the package we use at our University but it doesn't allow me to edit the steps names, I really wish it did because it would be so much easier. Thank you so much for looking at this and responding. Here are some detailed screenshot of those problem areas:
     
    Condition 8 where the loop seems to take issue. Here it weighing an amount and if it's over the dollar amount it goes to another approver level, if not it proceeds with the child flow. All the test we've been running are under and start the child flow. 
     
     
    The child flow trigger: 
     
    The child flow start:
     
     
    Where the loop seems to be kicking back and forth between HR and IBU:
     
     
     
    Then it just kicks it back and forth between those two for eternity.
  • David_MA Profile Picture
    15,099 Super User 2026 Season 1 on at
    What is the expression you are using in condition 8. When I open the screen shot to view the condition, it is to blurry to see what is entered, but it doesn't look like a valid expression. I could be wrong since it is difficult to read.
     
    Please let us know if your workflow has a do until action in it. Since you don't show the entire flow, it cannot be determined, but that is about the only thing that would cause a loop aside from using a trigger than kicks off the flow when an item is modified and you update the item as part of the flow, which is called an infinite loop. This post is several years old, but it still applies to how infinite loops work in Power Automate and gives several tips to prevent them from happening. You can read this to see if this is the issue with your flow; How to avoid infinite trigger loop in Power Automate.
     
    As for renaming actions, I cannot imagine that would be able to be restricted. I think the problem is that it is not intuitive on how to do this until you learn how. To edit an action name, just put your cursor in the title of the action and start typing:
     
    It will then change it in the flow view:
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
David_MA Profile Picture

David_MA 248 Super User 2026 Season 1

#2
11manish Profile Picture

11manish 204

#3
Haque Profile Picture

Haque 179

Last 30 days Overall leaderboard