Hi @yuhuisg Changing that value is not possible in an easy way. We have several websites and apps and also several development teams. Changing that value would be difficult. By the moment for testing is not possible.Yesterday, again I did a new testing. I'm sure something wrong with Rule. Look at this:

Hi @yuhuisg. In client side eVar24 is not assigned. But to be sure I did some changes to rule to remove explicitly eVar24 value when Flag=0. No result, issue still there.

Sorry, I mean we want to populate eVarY only when eVarX != 0 (not equal).To validate if condition position was the issue, we moved it last Friday to first section. But issue still there. Please take a look to this screenshot: This is last Friday implementation:I know, it's a small %. But we still think it shouldn't happen.

Thanks for you response. This is the thing.Someone in the company, before me, implemented a Processing Rule setting up the condition in "Then do the following" section. I don't really know the reason why. But we have an issue because we the idea is to setup eVarY only when eVarX=0. When checking the data in a Workspace Dashboard we find eVarX=0, eVarY=abcd. So, eVarY is assigned even when rule should filter it. Could be possible issue is because condition it's in "Then do the following" section ...