Thank you! Though I don’t understand github enough to see if this mean the fix will apply with the next update of the instances or if it’s supposed to already be deployed? If someone could clarify for me I’d very much appreciate it!

Thanks everyone for your confirmations. I’ll keep the workaround in mind in case this doesn’t get solved soon, and can confirm it worked for me before.