Hey @philmacaulay,
So sorry for the trouble! We are indeed aware of this and have a ticket open for it in our system and I have added this thread to it so we can follow up with you when a fix has been released. While I’m unable to pin a specific date for when it will be fixed, I do see this is a top priority ticket and, as such, our plan is to have it out in our very next maintenance release after 4.2 comes out (which is targeted for this week).
I’ll move this thread to Pending Fix in the meantime and we’ll follow-up with you when we have more information.
Thanks so much for the heads up and for your patience while we work on this.
Geoff