Hi Chris,
This is unfortunately a known issue with the current version, but the good news is that the fix has been developed and will hopefully be included in the next maintenance release (pending testing). I don’t have a timeline as to when this will be released at the moment, but I linked this thread to our internal ticket for this. As soon as we have an update, we’ll let you know here.
I apologize for the inconvenience this is causing! Thank you for your patience as we work on getting this resolved.