Great to see some posts on this threads, thank you guys for you thoughts.
--------
After testing it, clearPipeline seems to be the work around I was looking for. Thanks for pointing this out.
But now, back to my original question: why aren’t only input fields passed to a flow service and output fields the ones that should be expected?
Reamon, you write that the service signature in Flow is only useful at design time but why was the flow language designed like this? A “service” in general should be fully defined by its signature…
Is this a “feature” wanted?