@bfiander We are aware of this issue, and our development team is working on a resolution. We appreciate your patience.
