William

Hello, I think that we (my team) are in the same context as @PascalSchumacher describes in his related issue: #2171, meaning that we use history level `none` (to minimize DB...

Hello, No news about this strange behaviour? Here's a log (generated by running my 5 branches test file): [TEST_JUNIT_INCLUSIVE_ASYNC_EXCLUSIVE 5 branches.log](https://github.com/flowable/flowable-engine/files/3226660/TEST_JUNIT_INCLUSIVE_ASYNC_EXCLUSIVE.5.branches.log) Thanks Best Regards William

Hello Tijs, First of all, thanks to your team for the bug analysis 😁 About the issue, it is a problem when it is the external event thread which is...

Hello, Still no solution for this bug concerning the parallel execution with optimistic lock exception? What is strange to me is that it seems I'm the only one to raise...

Hello, Glad to see that this workaround can now be used without this new hashmap bug. :) But the question remains the same: there's still no true solution allowing to...

Hi, I have a question about such behavior: if we set the "join" gateway (final of the parallel gateway) as "Async" and "Exclusive", is it only the "join" job which...

**BTW, there's a bug at least in the 6.4.2 modeler:** when I set both Async and Exclusive flags to the join parallel gateway, then export/import the BPMN, both flags are...

Hello, I come back on this problem because we still have it. The new example is the following:  I have an inclusive gateway with several branches activated. Each one...

@GeorgiPetkov be careful because it's not only the **HI**story tables which grow, there's also **ACT_RU_ACTINST** which is the runtime history of all activities and grows a lot when you loop...

Hi, I have the same problem using a simple process with 1 Camel task in Flowable 6.4.0. I have installed the 4 Flowable wars in my Tomcat, everything works fine...