Hi!
Why flow skip my DeleteRequest ServiceTask in current schema?
Hello @Yakiv_Stoikov ,
at first glance, I cannot tell you why.
Please provide the bpmn xml, this allows us (the community) to provide you with more information.
Jonathan
Hello guys!
@Yakiv_Stoikov
I took a quick look at your flow, and it seems to me that your mistake might be because a ‘Parallel gateway’ always needs another ‘Parallel gateway’ to close the tokens created.
A parallel gateway divides your instance into ‘2 tokens’ to follow two different paths, but you need to close it again to join the ‘2 tokens’ into one again, and you do this by them meeting at another of these same gateways.
Every time you open one, you must close it before finishing.
Notice where I marked in red on your flow… at each of these points, your instance is dividing, but at no point are they crossing again to join together.
Think about it!
I hope I was able to help you in some way.
Regards.
William Robert Alves
I don’t think this is true. I’ve had model with just a fork and they work well.
2 Likes
Sorry Sir @fml2 and @Yakiv_Stoikov , I believe I didn’t know how to express myself correctly.
When you have some way to “terminate” the token it works correctly, no need to have a second “join” gateway.
What I meant is that when arriving at “task 2”, the token has already been divided at the gateway that is before “task 1”… and the question that remains is… “does camunda have adequate behavior for this?”…
“The correct thing would not be to leave the flow of “task 1” and join the tokens to later divide again in "task 2”.
I leave here a question that may be related to the problem… or part of it.
Anyway, I’ve never done it this way and I haven’t done tests on this model either to see if it would work or not. But if you still haven’t resolved it, it’s worth a change in this to test.
Maybe it helps.
Again I apologize for expressing myself incorrectly and perhaps causing confusion.
Regards.
William Robert Alves