Has this been happening to you at all in the last ~12 hours? That's when v0.31 went live and attempts to fix this