Problems getting started error message on every workspace

Hello,

A quick update on workspace creation failures.

We are actively rolling out a change to address Loop ability to be configured with Conditional Access policies. This will only apply to E5 licensed customers who are using CA to control access to apps. We can verify that these customers will continue to see Create Workspace failures when CA is used in their tenant. Please let us know if this is your case so we can keep you updated on upcoming changes.

If you aren't using CA and continue to hit create workspace failures continue to share your session ids.

Lastly, we did identify another error related to users who login with Shared mailboxes. These accounts will receive errors when they create workspaces. We will not address this case at the current time. Please use valid tenant accounts or MSA (for non-Commercial access) to access Loop at this moment.

Thanks,
Derek

Dear Derek,

Can you please help us? we are still facing the issue.

Please find the info:

Session id: a8c0610b-9909-4fc4-bca3-031284ada706

App version: 20230605041.001

Thank you

John

Good evening all!

Thanks to all of you who posted session ids today! We actually had an issue this morning that blocked all workspace creation and adding/removing members. This issue is now resolved and was unrelated to the issues we faced at launch with Getting started workspaces that prompted this original post.

We appreciate all of you who shared session ids today. However, these failures are unique to the issue we resolved this morning. You should be back in business for creating workspaces and managing rosters now.

If you are still failing to create Getting Started workspaces or shared workspaces, please share the session id.

Thanks,
Derek

Same problem here.

Thanks in advance! So excited to use Loop!

Session id: 3a30c1ed-68b4-4614-b205-d1282c68237a
App version: 20230531059

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

Hi Derek,

Session id: 13f588da-e539-42d1-ba66-1aef8f0f4272

App version: 20230531059

Our team uses Loop without Conditional Access policies. We've been experience the Oops problem for quite a long time. It appears to be slightly different to this particular report as we can create workspaces and new pages within but we cannot create new pages in Ideas or existing workspaces. Here's a list of symptoms

1. When I create a new page in an existing workspace, I always see this error.
2. When I navigate to the all workspaces menu, I sometimes see this error.
3. When I create a page in Ideas, I always see the error.
4. If I create a new workspace and new page within it, I do not get this error but after a short while, the changes to the document are sometimes lost. For example, I create a page, set a title and some content, navigate away and return immediately to the page. The content is present at this point. I navigate away again for a longer period and return to find and Untitled page with no content. Note that refreshing the page does not cause the content to disappear.
5. I do not experience the issue on existing pages that were created before the first record of the error.

There's also some suspicious 401 responses in the developer console so I've made sure to try different browsers and clear cookies and cache to try and resolve the issue.