Workspace error, unable to load.

Anonymous
2023-11-22T20:17:35+00:00

One of my workspaces is error and unable to load or delete. Others are normal.

I checked the following page:

edge://workspaces-internals

and get the error code like this:

Spaces Event: connecting to workspace container failed.
chrome-untrusted://edge-fluid-untrusted/fluid-untrusted.bundle.js:103
{}
Spaces Event: Fluid Status Updated for Workspace
Fluid Local Collaborator:0
{"Failure Reason":10,"Fluid Status":"Failed","Workspace Id":"fa90b560-4107-4819-a62a-6a2e1eb18a67"}

For some reason that I cannot upload screenshot I'm so sorry.

Here is a same screenshot from others: example ,

I believe all problems can be fixed if I can delete that error workspace in some ways. In fact, there is no delete option for it on GUI, different from other normal workspaces.

Microsoft Edge | Browser extensions | Android

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 No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Anonymous
    2023-11-23T06:06:27+00:00

    Hello, Perdred

    Welcome to the Microsoft Community.

    Thanks for visiting Microsoft Community. 

    The issues on workspaces error  is out of reach of the response support community. It is more suitable for publishing on Microsoft Learn (English only), you can click on "Ask a question", there are experts who can provide more professional solutions in that place. 

    You can also refer to the following linksMicrosoft Edge Workspaces preview for consumer accounts now available

    Here is a link to the forum where you can raise specific scenarios and share your idea to help solve the problem. 

    Microsoft supported products on Q&A | Microsoft Learn I won't be able to help you, but I'll leave that question open in case one of our amazing volunteers has ideas for you.

    Best wishes

    Bobhe | Microsoft Community Support Specialist

    0 comments No comments