Service Task in parallel gateway failing randomly and moved to dead-letter job

Hi @nishantharun,
the execution is happening in parallel and both service tasks are trying to write their result to the database. When both executions are happening at the same time, the result is going to be an optimistic locking exception at the joining parallel gateway. As Tijs described here, you can have concurrency issues and you need to “set the joining parallel gateway to async as well in this case and exclusive = true.”. With this both async jobs are going to proceed only until the exclusive gateway and you don’t have the optimistic locking issue afterwards. A new async task will be created starting at the parallel gateway.

Valentin