Thank you for your response. Yes, I picked it up this morning in the mobile app, at the same time the same error was saved in the browser. I just went into the browser to make a screenshot and found that there is no error anymore, everything is working fine. It looks like the issue is settled.