I want to exit from "Apply to Each" for exit the loop.
In some case, the loop does not need processing items after specific item.
Thank you for suggesting this idea, it is a good suggestion!
It's very irritating if you can't terminate the flow...do until or creating a variable to check the condition is not useful when you are using multiple custom connector with multiple CDS operations to terminate the flow immediately when your web service is failing....
AAAAH... Microsoft should release it asap...hope they will.
Also from Microsoft point of view this should be high priority...
A lot of loops are wasted (Azure resources can be saved 💸💸💸) 🤓
So strange that this feature is still not implemented.
any update on this feature,
I have a parallel approval send to leadership using for each and wanted to terminate if any approver reject the request so the other leadership member don't waste their time on reviewing it if it is rejected.
need to exit from for each loop and terminate the flow.
any other suggestion until this feature is implemented?
I need this! Should also apply to Do...Until in addition to the Apply to Each.
Hi @Stephen ,
I am a relatively new user of Power Automate and I am well and truly shocked to find that this basic element of flow control hasn't been implemented. I am desperately seeking this feature - being a programmer myself makes this even more painful, knowing that there is a better way, a simple way that has been a part of flow control in every major programming language.
Please could you share some insight into why this hasn't been prioritised? I feel like not implementing this is a mistake, and clearly I am not the only one.
I think the reason this hasn't received as many votes as other ideas is because a lot of folks who use power automate (non-programming types) don't know what they are missing by not having this feature! I work with a lot of folks in my organization developing flows in Power Automate and many times we have run into situations where this feature would have been useful! Explaining this need to non-programmers is difficult because they don't see a problem with resorting to clumsy workarounds...If 5-6 steps in a flow can be eliminated with a single Exit from apply to each step, imagine the cost savings and the time not wasted developing complicated workarounds!
@danman864 I expected as much! Imagine the savings 😪
Well this and many other shocking fixes and gaps to be filled, just sitting, waiting for some good willing Microsoft developer to spend 1 or 2 hours to implement them. I think if anything is bad about Flow it is exactly this. Many of the activities are documented as not even working properly.
Well, this basic function has been here for a long long time.
But Microsoft seems not to listen to it.
My code just get much longer and complicated because of this ...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.