Answered

Missing ability to add actions underneath condition control

(0) Share

Report

Posted on by BaconBits877

I am using a condition control in my flow but underneath the yes/no options, there is no way to add actions for each. When I first add the condition control, the options are available to add different actions. However, once I add a dynamic response to the left of "is equal to", the "+" buttons go away. I've done this for many other controls in this flow without any issues.

Categories:

Building flows

missing.png

not missing.png

I have the same question (0)

All responses (4)

Answers (1)

Verified answer

wskinnermctc 6,519 Moderator on at

Like (0)

Report

There is a limit to the amount of Conditions or nested conditions allowed in a flow. I think it is like 6 is the limit.

You should rework the flow to not nest as many conditions.

If you are using Approvals it is a great opportunity to use a Switch control. A Switch is a control just like a Condition except the control is based on the output of a value instead of a comparison.

The Switch is the forgotten control which should probably best with Approvals than conditions. But all the examples show conditions, so people keep using them.

See how pretty my Approval flow is laid out? Not a lot of clunky conditions nesting.

Was this reply helpful? Yes No
BaconBits877 8 on at

Like (0)

Report

I thought we were on to something with the switch but I ran into the same issue when I hit the 3rd level of approvers. I think part of the problem is Power Automate automatically adds an "apply to each" control to many of my actions such as when I use a "switch". Any suggestions?

Screenshot 2023-0...

Was this reply helpful? Yes No
wskinnermctc 6,519 Moderator on at

Like (0)

Report

@BaconBits877 I don't really know what you are trying to do with your flow, but it depends on how your approvals are set up, like First to Approve, Wait for one response, Everyone must approve, Start and Wait.

I'm not an Approvals expert. But usually there is a something within an Approval that causes it to change to Apply to Each. In my example below, I am only getting a single approver at a time, but the comments causes an Apply to Each.

So I made a step that consolidates the Comments so that it can be used as a single item that doesn't trigger Apply to Each.

Single Approver Comments In a Compose Step - Use the Outputs of the Compose in the flow as a single item.

Here is a video I found quick showing the general concept of avoiding an Apply to Each.

Here is another video that is specific to Approval comments (It long because it is thorough, if you already have an idea you can jump to like 9 minutes.)

Depending on your Approval type and what you are trying to do, you will have to find out how you can consolidate results to avoid apply to each.

On the Microsoft Learn you can see all of the details about the different types of Approvals Actions and how they function. It is good to check because you might be using a type that would make things more difficult when you could just use another.

If you want more specific example I would suggest marking this post as solved since you know why the Conditions were limited.

Then you should make a new post in the Building Flows forum with some title like "Approvals Response Apply to Each Switch Condition Limits" explaining your approval process and showing screenshots where you are having an issue. Make sure you explain the number of approvers, like is it one after the other, group approval, and describe your process order.

Someone who is better at Approvals will probably see it and answer quickly. If you put enough screenshots I might figure it out.

(I recommend making a new post because the Summer Challenge credits solutions within 24 hours, so people have more incentive to look at your new question.)

Was this reply helpful? Yes No
BaconBits877 8 on at

Like (1)

Report

What I ended up doing was reworking the flow including replacing some of the condition controls with switches. I wasn't able to prevent the "apply to each" from appearing but, overall, it worked.

Was this reply helpful? Yes No