Our community is also having this issue. We put in a ticket that was responded to earlier this week with "Our team has identified a bug that is causing this issue. The engineering team is currently working on a fix and we'll provide an update once we have more information on the deployment of that fix." It appears this won't be a quick resolution based on the response, which is unfortunate as we are having to delay posts on our end.
... View more