This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Really excited to try but all our users are getting:
"Oops!
We couldn't save the Loop workspace and pages you've created. They'll be lost as soon as you refresh or navigate awya from this page. Copy anything from them you want to keep and paste it somewhere else. Then, please try to create this workspace again."
Any ideas on what is wrong?
Thanks in advance!
A collaborative workspace app in Microsoft 365 designed to help teams co-create, stay organized, and work together in real time across apps and devices.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Session ID: 5d58ca1b-4e91-404e-a209-322fa8edf13c
App version: 20230228099.06
Session id: 4d57a89e-e1b0-450b-9062-29daf34d0e9e
App version: 20230228099.06
User has an Exchange Online mailbox and is an Admin of our root SharePoint Online site, but still getting the error.
Thanks for continuing to look into this. If the team are still collecting Session ID's then please see below. This is a user with an Exchange Online license as part of the Microsoft E3 and full access to the root SharePoint root collection. We've only enabled the Loop policies for a selection of people on the Tenant but all are reporting this 'Oops' error. Thanks!
Session id: dbba50ac-2de9-457e-86a9-5b0a95a0fa42
App version: 20230228099.06
Thanks for sharing this information!
I want to end the week off, by saying Thanks again to all of you that have shared your session ids with this thread. I just shared the newest session ids with our engineers.
For users impacted by your configuration of the root site in SharePoint, we expect you to start seeing improvements during the month of April. It's positive to see that some of you have been able to get around this issue by providing access to blocked users. We expect this issue is fully resolved during the month of April.
For those having trouble with your configuration of Exchange licenses, we are working on addressing this. We don't have a timeline to share at the moment. We will start another thread next week to track users that are impacted by this issue.
Have a good weekend!