Dimitri Dupard

Here are the schemas reprensenting expected execution result and the workflow logic :  

Problem is that these two (or more) branches should finish on a final state (sometimes the same, sometimes different ones) without waiting for the other(s). I don't want a join...

I don't understand why this `nextstep` variable should be locked as branches context dictionaries are merged when branches converge : > In a workflow with parallel branches, the context dictionary...

I tried with your timers (`sleep 2` for `sleep_action` and `sleep 50` for `sleep_wf`) and I confirm I don't see the behaviour anymore. However when getting timers back to previous...

It means that one of your `sleep_action` hasn't been executed. If we look at the workflow file, you should execute `sleep_action` 5 times (step 1 once, then twice on step...

I also dug a bit into Orquesta too this morning ^^' I tried to reproduce the graph which is created by the engine with networkx. Here's what st2 outputs :...