Hey @stevev1 – sorry for the slow response here. I was hoping I might have a short-term solution here, but we’ve looked into this a bit and unfortunately for the moment all I can say is that we’re aware of the issue and why it’s happening, and we’re working on a solution.
Appreciate your patience on this, and apologies we don’t have a more firm time frame for addressing this.