Comment 1 for bug 1771777

I've been able to reproduce the same issue, although i have not had any error logs. This may be a backend issue that we are not tracking correctly.