We think we found the reason for this error and we are working on a fix now. We hope to have the fix deployed later this afternoon.