Fork condition getting set to false
Hi,
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.
Expression: .TotalPassedTokenPoints >= .TokenPointsNeededForTask
Values at the time of evaluation:
Value of 'TotalPassedTokenPoints' = 8
Value of 'TokenPointsNeededForTask' = 4
Expected outcome: true
Actual outcome: false
Both properties are of Integer type.
Can someone please let me know what could be the root cause behind such a case?
Part of the flow that is having this issue (intermittently, not always):
Tracer output:
Hi,
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.
Expression: .TotalPassedTokenPoints >= .TokenPointsNeededForTask
Values at the time of evaluation:
Value of 'TotalPassedTokenPoints' = 8
Value of 'TokenPointsNeededForTask' = 4
Expected outcome: true
Actual outcome: false
Both properties are of Integer type.
Can someone please let me know what could be the root cause behind such a case?
Part of the flow that is having this issue (intermittently, not always):
Tracer output:
The values of the properties are same through out the operation (checked and verified)
Can you please also let me know if we can avoid this scenario by using a When rule instead of Fork expression?
Thanks,
Apurba
Message was edited by: Lochan to add Category
Pegasystems Inc.
US
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?)