@Filip_K
Thanks for advising, things clearly are happening on Windy's side to resolve the issue. I'd thought already it 'd be an administrative issue of local origin.