I have seen a repeat issue where rules that use a custom table (as a .txt comma delimited) stop working if that table has a new column added. Just experienced this after adding one extra column at the right of the table (and can share a screen recording via email if that helps).
What I see is that any rules with conditions referring to this table just stop working. When I click on the custom table token, it still shows the original file to be read from and the options of "First line contains column names" and "Trim blank characters" are checked, but the table data appears blank in the GUI (see screenshot). If I uncheck the "First line contains column names" option, all the table data reappears again, BUT...and this is the frustrating part...it resets the "Match using column" to Column 1 - I have to change it back to whatever column I originally had the condition set to. If I exit this dialog without unchecking the option, it stays blank and any other conditions within the same rule will also show with blank data (same lookup table) in the same way. However, once I "trigger" the change with the checkbox to fix one of the conditions, it fixes ALL the conditions in the rule. Then I can save the rule, and all works fine.
https://drive.google.com/file/d/1RFkAWDZbuupu_384TOmtiM0I612vkcCJ/view?usp=share_link
This feels very fixable...it keeps the lookup table file reference, but it's just not coping with the new column being added even if that new column is after all the others. Frustrating, because I have dozens of rules that all break like this if I add any extra columns to that lookup table. I'd really love to see this fixed or if you can suggest a workaround? Let me know if you want the screen recording video (by email).