Hey @Torq,
You have my apologies for the delay in following up! We are aware of this issue and are currently investigating a solution as quickly as possible.
I’ll keep you in the loop as things progress, I thought it helpful to share the tracking thread on this issue as well:
Thanks!