Automation Condition overlooked with before / after values to trigger email workflow

I have a workflow rule that should only email a specific group when 1 of 4 values change.

The logic is this:

The problem is, anytime the table has a data change, it ignores the condition and sends users unwanted emails.

I’ve tried [_thisrowafter]; also with no luck. I have 3 other Automation bots in the same app, and they seem to work fine.

Lastly, i have similar logic in the Old “Behavior > Workflow” area that is working fine, using the same…

OR … old value <> new/current value


any ideas?

Make sure the =/<> quirk isn’t a problem.

I default the values to zero, so the left side should also have a value. I have similar logic in the old workflow, so I was wondering if it might have something to do with the new automation features. I’ll take another look and make sure it’s not the quirk and report back.

Thanks Steve



Je rencontre le même problème, avez vous trouvé une solution?



Please contact for help with this.

@Steve and others - I wanted to follow back up on this. Support provide me with this logic, and the bot appears to be firing correctly now.

(“x” & [_THISROW_BEFORE].[a])<>(“x” & [_THISROW_AFTER].[a]),
(“x” & [_THISROW_BEFORE].[b])<>(“x” & [_THISROW_AFTER].[b]),
(“x” & [_THISROW_BEFORE].[c])<>(“x” & [_THISROW_AFTER].[c]),
(“x” & [_THISROW_BEFORE].[d])<>(“x” & [_THISROW_AFTER].[d]))

I’m not sure what the “x” does, but support was aware of the issue. I’m not sure if this will continue to work after the issue if fixed (I think it will).

Happy App’ing


The “x” works around The Quirk: