<p dir="auto">I wanted to use the features of canvas (group, chord, chain ...) to manage my workflow.</p>
<p dir="auto">If we take the graph just behind, I didn't succeed to find a way to execute it without having double nodes for the dependencies.<br>
<a target="_blank" rel="noopener noreferrer nofollow" href="https://cloud.githubusercontent.com/assets/7586111/11546638/5c8c7dca-9903-11e5-9c17-199a349622bc.png"><img src="https://cloud.githubusercontent.com/assets/7586111/11546638/5c8c7dca-9903-11e5-9c17-199a349622bc.png" alt="graph" style="max-width: 100%;"></a></p>
<p dir="auto">Does someone know how to execute it this graph using canvas? How could I handle that?</p>
<p dir="auto">Consider the following (where A, B, C, D, E are tasks):</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="sub_A = A.s()
chord_D = chord([sub_A, B.s()], D.s())
chord_E = chord([sub_A, C.s()], E.s())
res = group(chord_D, chord_E)()"><pre class="notranslate"><code class="notranslate">sub_A = A.s()
chord_D = chord([sub_A, B.s()], D.s())
chord_E = chord([sub_A, C.s()], E.s())
res = group(chord_D, chord_E)()
</code></pre></div>
<p dir="auto">This creates two separate invocations for task A.  For many cases, we would want the subtask for A to be invoked just once, and the work shared.</p>
<p dir="auto">It seems that manually giving the subtask a uuid leads to the desired outcome, but it would be nice to have support for this in the API.</p>