Conditions Evaluating Incorrectly

(1) Share

Report

Posted on by VD-17022020-0

I am trying to add the Condition controls to my function, but it keeps evaluating incorrectly. For example it will evaluate the expression as true and then continue down the false branch.

Or it will evaluate incorrectly period. In the below example, both of the conditions evaluate to true, the entire expressions should evaluate to true, but it is evaluating as false and going down the false branch.

This has not happened before, and I am wondering if it has to do with this new UI update that is allowing us to see the parameters in the condition results function view.

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Vish WR 1,122 on at

Like (0)

Report
Copy link

Link copied!

@VD-17022020-0

reason for this behaviour could be due to data type mismatch .

Was this reply helpful? Yes No
Suggested answer

11manish 1,467 on at

Like (0)

Report
Copy link

Link copied!
Your condition is not truly evaluating incorrectly.

This behavior is caused by Power Automate designer UI inconsistencies or hidden data/type issues.

Validate using Run History, normalize your values, and use explicit expressions to ensure consistent results.

Few common issues:

Data type mismatch

Things that look true may not be:

"true" (string) ≠ true (boolean)

"1" ≠ 1

null ≠ "" (empty)

Example:

equals('true', true) → false

Hidden values (spaces / nulls)

Trailing spaces: "Yes " ≠ "Yes"

Null vs empty string breaks equality checks

AND/OR grouping confusion

UI conditions can evaluate differently than expected due to grouping:

What you think:

(A AND B)

What it may behave like:

A AND (B OR C)

Was this reply helpful? Yes No

Suggested answer

Haque

1,975 on at

Like (1)

Report

Copy link

Link copied!

Hi @@VD-17022020-0,

As @11Manish mentioned, evaluation sometimes confusing, please make sure the comparison of data types of both sides are smae. One example I alwasy set like here. Please see the internal behaviour of the expression and vs non expression declaration.



“false” is typed directly but not taken from Expression window	Code view the declaration

“false” is typed in Expression window	Code view the declaration, please note "@false" value

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!