Thanks for the report! We released a server fix for this issue a few days ago and it should no longer be occurring.