Rule engine error - This might never match using looping nodes

[Pranjal_m]

Hi,

We are trying to replace values in multiple columns by using iterative loops on column however the rule engine shows “This might never match” error and generates empty columns.

And if I select the column name from rule engine instead of the current column value the rule engine works, I am not sure what is the issue here?

[takbb]

Hi @Pranjal_m ,
If you are able to upload a small example workflow that exhibits your issue you’ll probably find more people are able to help. I’ve not personally seen that message before.

You may find this post of interest in terms of an alternative way of handling multiple columns in a “rule engine” although I don’t know if it will exactly fit your use case.

Rule Engine

This one is more luke-warm encoding but here is a new component I’ve been playing with: [image] You give it a set of rules in a single table. I used Excel for this purpose as it was easier to edit. They use exact Rule Engine syntax, and I’ve copied and pasted from all of your rule engines: [image] The biggest limitation would be performance on very large data sets because of the amount of Column Appending it has to do, which can slow things down significantly, especially on a la…

[rfeigel]

Your screenshot shows “121–151” while all the other rules have a single dash. Its highly unlikely that has an effect on your problem, but probably should be fixed unless that’s what you actually have. I’m with @takbb - some data and if possible your workflow would help.

[Daniel_Weikert]

Are your columns sorted? Looks like you can just write the current iteration number in the column without any rule engine.
br