Hey there all,
Thanks for taking the time to reach out about this. There’s a known bug in with our developers now and they’re working on a solution. We appreciate the reports.
The original poster has identified a possible work around, but the problem should resolve itself after we push a hotfix for the problem.