@xiangli-cmu I don't the previous code actually worked correctly. The problem is that it was grabbing the index from the parent node instead of the node it was going to watch. The "1000 histories" fix code simply grabbed the first node's index (which would be a lot more recent).

My new code grabs the index of the correct previous node which will be later than the first node's index. We still have the potential for the "1000 histories" issue but that's something that needs to be fixed at the source of the problem (e.g. the limit itself). The previous code didn't actually fix the 1000 histories issue.