Hi Manuel_81,

That's probably linked to the known issue flagged in this thread. The team is working on it. We're sorry about the inconvenience. We'll be posting status updates there so please keep an eye on it.