I have a sub-workflow with two inputs. When I refresh/modify one input of this sub-workflow the workflow get freshed. Unfortunately not everything. The second input is not refreshed and if there is a TableRow to variable loop start for example then this node doesn't start fresh but rather where is stop the last time... This is somewhat counterintuitive as it is not visible from outside the sub-workflow that it still needs to be refreshed...
If you mean "reset" by refresh, then, I guess, this is expected behavior. It should behave very similar to the case where you have the content of the meta node in the top level workflow. If you then reset one branch, the unconnected branch will stay executed.
I understand where this is coming from but I still find it a bit counterintuitive. I basically behaves completly different to a real single node. Here, if one input changes the whole node changes and will have to be executed completely. But with the meta-node it looks the same but is not behaving the same. That is why I believe it is not 100% intuitive and therefore dangerous.... I would suggest to have a colored input that shows green, yellow, or read for example this would probably make things cleaner...