On primaries, when our new config matches the old config aside from term, we skip some of the validation checks and in particular, we skip calling isSelf to find our own entry in the config (since it must be at the same index). This avoids doing a round of network calls to all other nodes for term increases associated with elections, which is especially important since a likely reason for an election is a node is down and may time out in the isSelf call, slowing failover.

On secondaries, the heartbeatReconfig path does not do this check, which can result in the secondary not installing its config for a while.