@TapoNL It seems like the only solution is to reach out to support. Has anyone here managed to fix it without contacting support? If so, what did support do to resolve this issue? Could you share...