Hi all, providing a brief update here. As noted before, the team is aware of this issue and is working to resolve this. The team is still investigating and testing a possible fix. Once we can verify that the fix works and is safe to deploy, we will follow up. We know this is an inconvenience and we appreciate your patience as we work through this.
We have added this to the Dev Tracker for visibility.