Hi everyone, looks like the engineering team deployed a fix for this a couple of hours ago. Let me know if the issue persists