Open
Description
Current Behavior
Currently there is a afterJob
method in JobExecutionListener
that is called after the job completes but BEFORE the job metadata (status) is actually saved into the database. We currently use this method to send a message to RabbitMQ with the status of the job but there is the edge case that we send the message with the new status but the transaction rolls back in the end. This would lead to the case that the status in the message and the status in the DB do not match.
Proposed Feature
Additional afterJobSaved
method in JobExecutionListener
or configurable afterJob
method that is only called AFTER the job status is persisted.