@rzeta0 Hi! Thanks for updating the bug report – the QA community there can guess better at what the cause may be, than me on social media 😉