@vooslich Update on this issue; we have discovered a deeper problem and are working to fix it ASAP.