Iterables are getting miswired #163
Description
In at least two of my workflows, I'm getting a "miswiring" between inputnodes with iterables and later nodes (in my specific case, the wrong subject_id is getting assigned to the "container" input of DataSink, which renders my analyses rather worthless).
This problem does not consistently reproduce, although it seems to happen only on workflows with several sets of top-level iterables. There also appears to be some consistency in the items that get "miswired", although I have not been able to reproduce it using a subject-list with a randomly permuted order.
One possible reason? I set up several workflows and then run them separately (preproc, modelfitting, registration, fixed-effects), but the IdentityInterface node that provides my subject list remains associated with the first workflow. It feels like this problem happens only when I run multiple workflows in the same script.