We cannot guarantee that heartbeats always come back in the order they are sent. It is possible that a node responded two heartbeats at configTerm 1 and 2, but the heartbeat with configTerm 1 arrived at the receiver at a later point. When we process the heartbeat response and update member data, we are not checking if the configTerm from heartbeat is greater than the current one, which could cause a configTerm regression for certain node and lead to cases like BF-33998.