Error accessing workspace after removing default workspace using API


When trying to access other workspaces after accidentally removing the default workspace using the API, an error is encountered. The error message indicates that no workspace was found for the organization.


Hello all,

I have a doubt, I removed the default workspace using API by error.
Now if I try to access other workspace in UI changing URL I’m receiving an error. Is this ok?

If I execute docker logs against the container, I am getting this error:

2023-12-28 09:17:46 INFO i.m.h.s.n.h.a.e.AccessLog(log):125 - airbyte-webapp.airbyte_airbyte_internal - - [28/Dec/2023:09:17:46 +0000] "GET /api/v1/instance_configuration HTTP/1.0" 500 1555

2023-12-28 09:17:54 *ERROR* i.a.s.a.ApiHelper(execute):49 - Unexpected Exception
java.lang.RuntimeException: No workspace found for organization: 00000000-0000-0000-0000-000000000000
at io.airbyte.config.persistence.WorkspacePersistence.lambda$getDefaultWorkspaceForOrganization$7( ~[io.airbyte.airbyte-config-config-persistence-0.50.38.jar:?]

Thank you all.

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["error", "accessing-workspace", "default-workspace", "API", "workspace-not-found"]