Currently the stack trace printout is saved in the same transaction provided the exception is not related to persistence. This scheme has two drawbacks:

1. Exceptions not related to persistence may still leave the job and the process instance as a whole in an inconsistent state.
2. Persistence exceptions are never saved.

Hence saving the stack trace in a separate transaction would be preferable.