How to avoid all activities to be rolled back on Flowable Exception

Before diving into the points, one thing to note is that Flowable will transactionally move the process execution from one stable state to another stable state. If an exception happens during job execution, the engine will roll back to the previous stable state.

  1. How did you configure that boundary event? You probably will need to configure the script to throw a BpmnError when an exception is catched.

  2. The deadletter job has executionId, processInstanceId and processDefinitionId. The executionId can be used to fetched the Execution which points to the activity where the job failed.

  3. That is most likely because the transaction has been rolled back to the previous stable state.

  4. Correct, everything part of the same transaction will be rolled back.

  5. Can you elaborate on that, not sure what you mean?