Under certain use-cases where you may use a shared file read-lock idempotent repository for a active/active cluster setup of consuming files from a shared directory, then you may have the idempotent repo setup as readlock strategy. And in this scenario you may want to delay the commit/rollback operation at the end, to expand the processing windows of the given file to avoid other nodes to potentially be able to pickup the file as well.
This requires both a sync vs async way. So users can setup a scheduled thread pool that can delay the work for the commit/rollback so the same node can continue processing the next file.
By default this should be turned off.