Maybe they use some kind of response caching to save resources and the original pointer is now pointing to a newer response to the same question? Still would be

Maybe they use some kind of response caching to save resources and the original pointer is now pointing to a newer response to the same question? Still would be an insane way to do that for a history log unless they're trying to memory hole previous instances of past poor performances or wrong think.