Hey @edward, thanks for reaching out!
This is a known issue and we are working on a fix.
Thanks for your patience, Tommy