Interesting, possibly has the advantage of making the logic of your flow simpler, right ?
I see that the question of table refresh is recurrent (for example here). This issue was discussed in this forum in the past. I remember that we found two different ways to get round the problem. This is the link to the discussion.
It is not clear in my mind why the table does not auto-refresh when it is updated. This would be the expected behaviour in my opinion. It may be related to the architecture of the underline Tabulator library (and its complex virtual DOM) or perhaps something specific about the ui_node working in Node-RED dashboard.
Do you have a simplified flow that reproduces the issue you are facing ? I could try to make a couple of tests to see if the workarounds found in the past may help you.
