Problems getting started error message on every workspace

Anonymous
2023-03-22T22:27:08+00:00

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!

Microsoft 365 Insider | Loop | Windows
Microsoft 365 Insider | Loop | Windows

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.

0 comments

173 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2023-04-03T14:56:36+00:00

    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

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-04-03T17:15:50+00:00

    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.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-04-04T18:17:17+00:00

    Session ID: 5d58ca1b-4e91-404e-a209-322fa8edf13c

    App version: 20230228099.06

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-04-06T21:55:27+00:00

    What is the status of the fix?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2023-04-07T00:14:56+00:00

    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!

    Was this answer helpful?

    0 comments