2 weeks ago
Hi Barbara,
Thank you for your question.
The deadlock is created because end-events are modeled within the parallel gateways. A parallel gateway always waits for all tokens that were generated at the beginning (here 3). However, due to the X-OR gateways and end events, it is possible that only one token arrives at the merging parallel gateway. Therefore, it is a deadlock, and the process flow does not continue.
To remove the deadlock, the process would have to be re-modeled, or a complex gateway would need to be used for joining. However, it must then be clear when the process flow should continue, i.e. after how many tokens.
Please note, in our Onboarding Resource Centre, under Enablement, you can find E-Learnings and further documentation regarding these modeling conventions.
Best regards,
Katie
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
67 | |
8 | |
8 | |
6 | |
6 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.