Checking in with an update on this one. We’ve been working on it since it first started happening, and it was due to a very rare (and hard to reproduce) bug. Last night, we fixed the bug so that this should not happen again for anyone. We’re now moving on to determining what we can do, if anything…