We’ve been able to reproduce this issue and we’re just waiting on a dev to free up to work on fixing it. The fix should be included in a release Tuesday-ish (24th).
Thanks everyone for submitting multiple support tickets; we weren’t able to reproduce the issue right away and the additional information really helped speed things up.
Remember, if you experience a bug - create a support ticket!