Column Resorter node Problematic Behaviour

When the Column Resorter node is used in a workflow and then this subsequent workflow gets additional columns added, it causes the Column Resorter node to error.

Ideally, the node should keep the originally defined column order and the new columns appended at the end of the ordered list. Causing an error from column changes makes alot of workflows break and so I generally try to avoid using this node because of this.

I'd really appreciate a fix.