We are currently using version 6.4.2 of flowable engine and have an issue with the retry logic.
We implemented a javadelegate which is triggerable and marked as asynchronous and triggerable in the model.
The execute method of the delegate sends a message to a message queue (rabbitmq). Another application then processes this message and sends a message back to our flowable service.
When it receives a message for the execution an async trigger is called for the specific execution. In case of failure the trigger propagates an exception so the service task goes to the deadletter-job queue of flowable.
The problem is when we use the move-job action to retry the job only the trigger part is executed and not the execute part so the job is actually not retried just the trigger.