In WT-7813 we added an additional condition to the loop that writes updates to the history store. Previously we would always iterate until the end of the updates stack, but now there are cases where we exit the loop before we reach the end. We do not clear this structure before iterating for the next key. It seems like the issue seen in BF-21876 is occurring because we are reading updates that should have been cleared already.