Camunda parallel gateway does not wait for all sequence flows
I am implementing a bpmn process with camunda. My Workflow looks as follows:
As you see tasks A, B and C are user tasks which need to be completed. Sometimes these tasks need to be repeated so i modify the process instance via the rest api.
This modification then starts before the task/activity that has to be repeated.
Now if you complete task A 3 times because you want to repeat it, the parallel gateway no longer waits for all sequence flows to be executed and just triggers the terminate event (needed to kill the trigger notification service task above).
As i understand this seems to be the behaviour of an inclusive gateway, which just waits for a certain amount of sequence flows to be executed. But the parallel gateway should wait for every single one of its joined sequence flows to be executed as far as i unterstand it.
Is this behaviour known?
The BPMN 2.0 specification section 10.5.4 "Parallel Gateways" says:
For incoming flows, the Parallel Gateway will wait for all incoming flows before triggering the flow through its outgoing Sequence Flows.
so technically your expectation is correct. The engine only waits for a number of tokens equal to the number of incoming sequence flows and therefore you get the observed behavior.
How you are work with a repeated execution (and also the trigger) is rather uncommon. Why don't you make the possibility of repeating the task visible in the process? You could for instance attach a message boundary event and loop back into the task (A in your example). Then use the message API instead of the more invasive modification API. This would lead to a process model which better reflects what can happen. Other alternative options to model this better instead of using modification API include BPMNError, Escalation, xor gateway following task, embedded sub process and more.
- How to use `async for` in Python?
- FastAPI runs api-calls in serial instead of parallel fashion
- Boost asio, timer inside async_receive_from wont trigger
- Can you test whether a function is actually running Asynchronously?
- Task return type with and without Async
- Why do I get "expected type Future" error using match statement on Result?
- Why do we need async and io_context?
- How do you execute code when scene goes to background using new Swift async/await concurrency model?
- Guaranteed Semaphore order?
- What is the difference between concurrency, parallelism and asynchronous methods?
- Python asyncio: Concurrent write tasks frequently canceled, how to ensure alternating execution?
- How can I run a async enumerator method synchronously and store it as an IEnumerable?
- When correctly use Task.Run and when just async-await
- SSH.Net Async file download
- Async methods throws "Implementation of JAXB-API has not been found on module path or classpath"
- How can a Callable return a value from a predefined void callback?
- How use async function in angular 17 function based Http Interceptor
- Why does `promise.finally` execute after its caller's `then`?
- How can I add a connection timeout with asyncio?
- Using Func delegate with Async method
- How to sequentially chain two sync iterators in JavaScript?
- Using a coroutine as decorator
- Is it some way to do async code for write to Stream?
- .NET C# async await. whenall does not wait for tasks
- Why is my asyncio task not running concurrently in Python?
- Swift concurrency: 'for await' does not compile, 'await' has warning
- Dart Future.wait for multiple futures and get back results of different types
- Retrieving results from finished multiprocessing task as it has finished
- How to return in an Async Function in Angular?
- Asynchronous scripts execute after deferred