Hey hey,
currently working on a project where I use workflow invocation (for now locally).
I have encountered some weird behavior:
- I’ve set up the WF to be called with corresponding input nodes:
and output nodes:
- In my WF that I use to call the other WF I use Call Workflow Service node, point it to the workflow to be called and then start changing the order of input/output ports - e.g. from this:
to this:
And click the adjust node ports button.
- I run the Call Service Workflow and it executes successfully
Now I save my workflow and then re-open it. As long as I never open the Call Workflow Service Config menu again, everything seems fine, the moment however I open it, the input /output port order seems to be reset. If I then accidentally close out of the config dialogue with “OK” or “Apply”, then the next time I run it, the WF fails as the inputs end up hitting the wrong WF branches. Only when realizing this in time and hitting “Cancel”, it keeps working.
I have set up a minimal example that should allow you to reproduce:
Call WF Service Min Example.knar (187.1 KB)
If it is not a bug then I’d appreciate for this to be taken as a feature improvement request :-).
Update: I also noticed that sometimes when selecting a callee workflow this error shows up and the ports can’t be fetched:
