It is sometimes stuck on the stage as depicted in the picture - the timer. The timer is set to fire every two minutes. By stuck I mean that no log entries are written for hours, although every task prints to the log so I deduct it must not execute. The process instance might be stuck on the very first time the timer is started.
Getting it unstuck is possible by: deleting the existing process instance and starting another process instance (works some of the time), starting another process instance of the same workflow in parallel (without deleting the original instance).
There is usually one or only a couple of process instances running in parallel.
I’m using Camunda 7.12 community.
No, there is no cluster.
What do you mean by the job executor properties and how do I get them?
I deploy and start the process using these commands: