We now have a fix for this thanks to some dedicated community members.
This fix will be incorporated in the next major update.

Thanks for the help!