Hi All,
While trying to revert a process to previous user tasks which were completed within the parallel flow, the token doesn’t wait at the gateway for the other flow line to reach. I know that camunda validates if all the tokens have reached (which already did during initial flow) and hence doesn’t wait. this is known behaviour.
Can anyone suggest a way to clear the path followed or delete the tokens generated earlier? if needed, such a way to modify the below diagram to achieve the same.
Hi @syedkp
Could you provide more details, please?
Hi @hassang . I am trying to move the flow back using startBeforeActivity api. so what happens is, if I move the token to the user task in sequential flow it works fine but if I try to activate user task which is in parallel flow then as soon as one task is complete the token doesnt wait for the other parallel task to complete, rather it moves forward. Is there any workaround for this situation.
This is likely because you have used “Inclusive Joins” rather than “Parallel Joins”
This can be seen in your image where you have multiple flows flowing into a < O > gateway rather than a < + > gateway.
@GotnOGuts - I have updated the diagram. Basically, we need to move from 1 to 2. when we do that, the workflow doesnt wait in the Join post parallel gateway.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
