Timer due date not as expected

Hello,
we have noticed a weird behavior in our process.
We have defined a timer event where the instance is ‘parked’ for 2 days. At the end of the expected waiting time, the instance proceed to the next block.

We have noticed that, for some reasons we ignore, the due date doesn’t correspond to the expected waiting time. Please have a look at the images below

Task definition from the Modeler

has someone ever faced this issue ?
Thank you in advance for the help