Audit Event for S3 retention date extension

Because Fidelity complains that S3 extension does not work or does not work reliably it is requested to create an audit event that would report document id, binary digest, original retention date, extended retention date. It should be called after operation confirming action being taken. Right now retention extension date is not align with request params. Mongo Retention date is correct but S3 retention date either old (unchanged) or is taken from another request (multiple documents end up retained to the same incorrect date).  

 

 Retention date cannot be extended, and it is suggested to implement audit in the place where action is performed to confirm validity of the transaction context. I suspect that transaction context is corrupted (records collide, queue is malfunctioning, local implementation is not resetting its state before handling new request etc)