How to make two parallel wait nodes enter to waiting status at the same time?

[windy4312]

There are two parallel wait nodes in my workflow ,how to make the two nodes run at the same time?
there is just one wait node waitting at once, the other one will be waitting when I finish another wait node.

[Mookie_Lian]

Why not use one Wait node and then split the data? Can you give some context?

[windy4312]

Thank you for your reply. Actually there are two person in the workflow to finsh their tasks and there is no order of them who finish the task first, they can do it at the same time. I set the webhook suffix each of the two wait nodes. If there are not waiting status at the same time, the one of the no waitting wait node can’t be changed if the person finish this task. Only the first waitting node is finished then the other one can be updated. I tried not set the suffix then the url to update the wait node is the same and I don’t know which person finished the task.

[windy4312]

I tried to replace the two parallel wait nodes of two parallel subworkflow, but still there is only one changed to watting.

[Mookie_Lian]

I think I understand what your problem is.

My suggestion;

• Use a temporary store before these nodes that stores whoever finishes first. Then you can use a node that “Gets Data” from the store with an If node to check if both have completed their tasks; if they didn’t you attach the Wait node.

Second Option:

This could be much more unnecessary since there may be a better logic to solve this problem but;

• How about turning this into two workflows, one for the first and one for the second task; and then make a third collector workflow that waits for both to finish?

Note: I’m not sure if these would work because I haven’t really caught up with the problem. And I can’t make example workflows on my own since I don’t know what triggers these webhooks. But nothing bad comes from trying.

[jcuypers]

Hi, I might be wrong but I think there is a “wait for result” option on the sub-workflow execution. Maybe if you turn that off it might actually do what you intend it to do.

Reg
J.

[windy4312]

This is an example of an application scenario where we want to achieve that after the manager’s approval, both the HR Director and the Finance Manager receive notifications simultaneously and can operate at the same time. Currently, whether using two parallel ‘wait’ nodes or two parallel sub-workflows, it is impossible to trigger them simultaneously; only one can be completed before the other can operate, making it a sequential operation rather than a parallel one. The core objective is to enable these two roles to receive notifications simultaneously (here, the configuration of HTTP notification nodes is omitted) and to be able to operate at the same time.

[Alper_Gondiken]

I’m actually looking for an answer to the same problem.

Normally, jcuypers’s answer is right, you can turn off “Wait for result” toggle in the “execute workflow” nodes - this runs the two in parallel. but the issue then is that it doesn’t store the data from these two nodes. so any subsequent node can’t use the info from these workflows. I’d love to hear if anyone comes up with an answer to this issue.

[jcuypers]

Hi, an external data store could bypass this issue. In essence, the whole issue can be bypassed if you don’t need the exact timestamp. If you log each subprocess data with a unique uuid you can correlate the results afterwards and take that timestamp. Imho you just need a common correlation. The way to store and retrieve is a bit overkill but at least it’s transparent and easy then debug

Reg
J.