@anon5074910 Can you check with the lastest beta release - it should be fixed there now. Just run a refresh metadata.