Bleh. I can’t reproduce this issue even with an account on that instance.

Edit: I’m going to push out a release with more logging. In the past I added some logging to try to capture this error but I think the error is somewhere else where I am not capturing errors.