When a transaction commits or aborts, it does not destroy the RecoveryUnit on the OperationContext. That RecoveryUnit still contains the _readAtTimestamp from the transaction. When we profile at the end of the command, we attempt to open the WT snapshot at time _readAtTimestamp. But since the transaction already committed/aborted, that snapshot can be destroyed, and we can get at SnapshotTooOld error. The RecoveryUnit for profiling should not have _readAtTimestamp set.