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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-06-12T20:09:56+00:00

    Thanks for the updated session ids.

    Our team is currently investigating issues with Conditional Access policies impacting workspace creation for certain tenants. The problematic configuration analysis is not complete. We will update again when we have made updates that we can deploy to production.

    If you are not using Conditional Access policies in your tenant and you still have these problems, please continue to share your session ids.

    Thanks,
    Derek

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-06-03T08:44:48+00:00

    Hi Derek

    Same error for me :(

    Session id: cfa24e62-1944-4c07-9cce-9eedb06f8ad8

    App version: 20230525012.002

    Thanks

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-06-02T12:27:42+00:00

    Oops error here too.

    Session id: 429a4906-687f-42de-9ac4-e5cf8b4c893b

    App version: 20230525012.002

    DevTools shows 403 error for https://substrate.office.com/speedway/v1.0/workspaceGroups

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-06-01T15:04:24+00:00

    Hi Derek,

    My instance seems to still be affected as well. Here is some info to hopefully help.

    Session id: cf0eeff1-3ba0-4d18-b788-83b1c6acb14a

    App version: 20230522030.001

    Thank you!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2023-06-01T14:55:59+00:00

    Please share your session id so I can review your case with our engineers.

    Was this answer helpful?

    0 comments