The durable timestamp for a transaction persists across multiple transactions. This can lead to out-of-order timestamp failures during fast truncate timestamp validation, where this outdated timestamp is incorrectly assigned to updates.

To resolve this issue, we need to reset the durable timestamp at the beginning of each transaction and avoid setting update timestamps for transactions that don't have one