I discussed your issue with the dev team and they confirmed digests recalculation shouldn't be triggered by replication job fail.
Also, the replication job should use CBT similar to the backup job behavior.
Thank you Dmitry for your message. Hmm, maybe I'm little bit confused about this... I think there are two different things to consider:
Calculating digests (e.g. in case of increased disk size of the source vm)
Reading whole content of source disk (do not use CBT)
I checked it again and the last entry is the case when the job hasn't been successful before. In the history I can see a replication job, which is titled as "Retry 1", which has the following entry within the job details:
Cannot find dirty block information in the previous restore point, CBT will not be used
Why is CBT not used when the job failed before? As I mentioned before, I cannot see a differenct between replication and backup if we are talking about this behaviour.
Thank you, Regards