Support
(@techtt)
4 years, 5 months ago
It was resolved by WordPress.com support by clearing website cache.