Ok, it came back up but I’m guessing this is after the leader did a snapshot .. so in theory when this race happens I can force the leader to snapshot with an API call and then clear data and re-start the sever and it’ll be ok (that’s my theory)