Hey @bigorangecat - thanks for the bug report and sorry for not replying sooner!
This was a regression that was introduced, but we do have a fix in a Beta build with the fix being pushed to stable soon.
More info is in this related bug report, so I’m going to mark this one as solved!