In our application we are using a parallel gateway with async service tasks, and no user tasks at all. Turns out his is causing optimistic locking exceptions when writing variables to the executionContext.
The solution suggested a few times on this forum is to mark async tasks as exclusive. I can confirm this helps, but it also looks to me this solution also takes away the advantages of using parellel streams. Am I missing something?