The way that the @CronTarget annotated cron job methods catch (Exception e) and then do throws JobExecutionException looses the root cause(s). This makes fully understanding and debugging e.g. (one of) the problem shown in
FINERACT-857, for a solution like FINERACT-859, more difficult.
I'll try to fix this in this issue (just the error logging, not the actual problem).