Answered

ActionBranchingConditionNotSatisfied error when it seems to be satisfied

(0) Share

Report

Posted on by SaraMahan

Hello I have a workflow that is stating ActionBranchingConditionNotSatisfied when the conditions seems to be met. I am not sure if I did something wrong or if it's an invalid error. The flow is running successful until the actions after the condition, they are getting skipped. I added get properties>compose>condition. My condition is if field_17 = true. My compose is "Has Column Changed" The compose input/output are both showing true for that field but it's saying it wasn't met. Screen shots of my entire flow, my condition parameters, inputs/outputs from my compose action showing true and the condition showing false...

Can anyone tell me why it is not meeting the condition as true when the field is marked true in compose action? Thanks for any help!

Categories:

Building flows

I have the same question (0)

All responses (9)

Answers (1)

David_MA 12,982 Super User 2025 Season 2 on at

Like (1)

Report

What type of field is it in your SharePoint list? If it is a choice or text field, you will need to do something else. If it is a Boolean yes/no, true/false, then your expression should be working. You could try using the following expression on the left side of the condition: equals(triggerBody()?['field_17'], 'true')

Was this reply helpful? Yes No
Suggested answer

Pstork1 68,739 Most Valuable Professional on at

Like (1)

Report

Based on your first screenshot I think the problem is that you don't have anything inside the No side of your condition. So if the condition evaluates to false there is nothing to do so it reports that the 'Action Branching Condition is Not Satisfied'. Try adding a simple Compose action to the no side with a static value and see if the error doesn't go away.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
David_MA 12,982 Super User 2025 Season 2 on at

Like (1)

Report

@Pstork1 I don't think the issue is with not having any actions on the no/false side of the condition. The screen shot says the condition ran without error as indicated by the green check, and the actions on true side are grayed out indicating those were not processed. In fact, nothing in the screen shot provided shows where the error occurred.

@SaraMahan can you upload a screen shot of a flow run and show the action that generated the error? It will be highlighted with a red exclamation point. Then also show how that action is configured.

Was this reply helpful? Yes No
SaraMahan 8 on at

Like (0)

Report

HI David MA(it won't let me tag you for some reason)Thank you so much! I think you nailed it with the boolean vs string. It is a choice column. I don't think it could be the condition no is blank as I have that in other working flows. Screen shot of action and full flow below, but it's not technically an error, it's getting skipped. There is a message at the top of the skipped action though. I tried using your equation: equals(triggerBody()?['field_17'], 'true') but am getting the same result. The flow is showing successful, no errors/exclamation marks, just two skipped steps after the condition step. Any thoughts on why?

Action that is getting skipped

Complete flow showing success until "Update Item" step.

Was this reply helpful? Yes No
Verified answer

David_MA 12,982 Super User 2025 Season 2 on at

Like (0)

Report

@SaraMahan if the field is a choice, then in the expression you need to use the field from the dynamic content that has value after it rather than just field_17. The updated expression would be equals(triggerBody()?['field_17']['Value'], 'true')

If you put the two options into a compose action, you will see they return different content.

Was this reply helpful? Yes No
SaraMahan 8 on at

Like (0)

Report

Hi David - one more question - for the expression equals(triggerBody()?['field_17']['Value'], 'true'). I was told before to choose the "has column changed" from dynamic content in the compose field and put the expression in the condition field after the compose step but based on your last comment should the expression be in the compose field instead of the condition? Or in both?

Can't thank you enough for helping me out!

Was this reply helpful? Yes No
David_MA 12,982 Super User 2025 Season 2 on at

Like (0)

Report

I think I am slightly confused by your latest post, @SaraMahan. Is the condition in your flow supposed to check if this field was revised when the item was modified, or to check if the value is true, or both? What you need to do depends on this. I am guessing that you want to check both based on your flow diagram. If so, add new item to your current condition. Then go into the Dynamic content and look for the value from the get changes for an item corresponding to field 17. It will say something like, Has field_17 changed? It returns a Boolean value of true/false. Add this to the condition and set it to where it is equal to true as well, but enter true from the expression builder like you originally did.

The condition will then check to see if field_17 was updated with the last modification, and that the value of field_17 is true.

Was this reply helpful? Yes No
SaraMahan 8 on at

Like (0)

Report

Sorry for the confusion.

Currently I have this dynamic field in the compose action - but my question is should it be the expression you provided instead of the "Has Column Changed"

And I have the expression you provided in the condition action but now I am questioning if I have it in the wrong place. Should I have something else here or should the expression be in the Compose and the Condition actions?

Hope that makes sense!

Was this reply helpful? Yes No
David_MA 12,982 Super User 2025 Season 2 on at

Like (1)

Report

As you are using the compose action in this flow, it doesn't really do anything except allow you to see the values passed from dynamic content. The condition is doing the actual logic in your flow. You can delete the compose action and it will have no effect on your flow unless you are using the output from it in your condition.

Was this reply helpful? Yes No