Multimple "action in" work only with "out"

[drozel]

Hi guys. First, many thanks for this lib, it's really useful.

I'm trying to use it to build my own logging trough all tabs. The idea is simple: I gonna put 'action' nodes everywhere I want to log something and 'action in' where I want to read logs, e.g. to put them onto the dashboard.
Here is my example: 2 log 'writers' and 2 readers putting them in log for debugging.

Unfortunately it doesn't work: only one 'action in' with lowest priority is called after injection:

It works if I put 'action out' after each 'in':

But in terms of 'extendability' you mention in the documentation, I can't guarantee that every user listening my events with an 'action in' puts any out after that. It means, every 'client' can break entire injection mechanism.

Or I did understand it wrongly and there is another solution?

[Steveorevo]

I see the issue here. Currently there is no way for a subsequent flows to be invoked if there is no return back to the main thread; flows won't know when the first one is 'done' and to continue to the next. A timeout could possibly be implemented; but that would degrade performance if clients don't comply otherwise.