Hi @Phil88
Thanks for posting — it looks like this issue is only happening in Safari.
Can you please try using Chrome as a temporary workaround while our team continues to investigate the issue?
Thanks in advance, and we’ll share more details as soon as we can.