Ya seems like a uncaught scenario of job executor racing with it self:
Run 1:
Run 2:
The instances dont match the “expected” result because of the bad job executor config, but that sort of makes is “Execpted”.
The real issue here is that the issue seems to happen only on the first run of the process def after a deployment. On a second, third, fourth run, it does not occur.
Simple BPMN for testing
lunch.bpmn20.bpmn (10.7 KB)