Hi,
Thanks for the report.
Confirmed, we’ll get this resolved for v6.4, which will be released as a hotfix tomorrow.