Hi Cryptocurv,
This is due to a (benign) bug in the catchup logic. It should not affect the actual catchup or agreement. Regardless, it has been fixed and V3.2.2 has been prepared and I expect it to go to BetaNet Monday with a stable release coming another 48 hours later.
Ben