We are currently observing an issue which is caused by a fork condition getting evaluated as 'false' intermittently even when it should not be the case. Just wanted to ask if this is at all possible. I have tracer output from production which is showing that the values are proper to evaluate the condition as true but it is setting as false.
Hello Apurba, Certainly strange behavior. The expression looks valid. Since the page isn't specified is it possible these properties one or both are defined on another page in which the values are different. Since you captured a trace does that mean you can reproduce or regenerate the behavior. Could you via private checkouts attempt to pipe out to the logs the values on the expression prior to evaluation? Are these properties coupled to any declaratives that could be modifying them during the process? (When traced were declaratives monitored?)