Hello everyone,
We’ve recently observed a strange behavior in our workflows where the “Compare Strings” operator’s comparison type has automatically changed from “Contains” to “Matches”, without any manual modifications.
Interestingly, despite this unexpected change, the workflows continue to function as if they were still using “Contains.” However, we are concerned that this could introduce side effects in the future.
Has anyone else experienced this issue?
Additionally, we are curious about the exact difference between “Matches” and “Equals” - does “Matches” support regex patterns, for example?
Would appreciate any insights or official clarification on this!
Thanks in advance,
Youssef Aghzere
