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.
I encountered CORS failed while trying to open a workspace.
Request:
Response: CORS failed
I hope this helped.
To make no complicated and more OOOPs. sorry I can't work with this new program. It seem that the team work in how to make useless
The issue has now been resolved for us and we are able to successfully work in Loop. I'm not sure what changed but if the team at Microsoft had anything to do with it then I'm very grateful 😁
A quick update from Redmond.
We have passed along the additional session ids that came in this week. Thanks for sharing. We have 2 fixes that will be rolling out in April. The first fix is for users that don't have an Exchange mailbox. We expect this to complete deployment next week. At that point we will start looking at telemetry to verify the fix is working.
The second fix for users that don't have access to the root site will start rolling out next week but will take multiple weeks to roll out to all data centers worldwide. We should start seeing positive results next week, but we will be closely watching the global roll out before we close this issue.
To be clear we aren't looking at 1 fix to address this. There have been multiple fixes deployed to this point and we can quantifiably see their impact in reliability already. Most of the issues reported by session ids this week are aligned to the known fixes coming. Once we deploy the next set of fixes, we will continue to look at any remaining issues and prioritize them accordingly.
Thanks again for your patience and helping us work through this!
What is the status of the fix?