Workspace Git Sync Error - Unable to initialize your workspace

Hi anmerk, 

Can you click the "show details" on that error message and let us know what it says? This will help with troubleshooting. 

Can you also confirm what worksapce type this is? You can see this in the workspace settings -> workspace type. 

Lastly, can you confirm if you are using GItHub or DevOps?  By default only DevOps is allowed, perhaps your admin turned off GitHub after you configured it and that is the cause? 
 

Hi anmerk​,

Thank you for reaching out to Microsoft Fabric Community.

Thank you ShivekMaharaj​ and tayloramy​ for the prompt response.

As we haven’t heard back from you, we wanted to kindly follow up to check if the response provided by the user's for the issue worked?  or let us know if you need any further assistance.

Thanks and regards,
Anjan Kumar Chippa

Hi anmerk,

The fact that the same branch works when you connect it to another workspace is useful here. I would focus on the DEV workspace's Git initialization state rather than changing the repository first.

Fabric separates the Git connection from the initialization/sync step, and Microsoft's Initialize Connection API documents workspace-side failures such as WorkspaceHasNoCapacityAssigned, MissingInitializationPolicy and InsufficientPrivileges.

Since you have already disconnected and reconnected it, I would open Show details on the error and capture the actual error code/request ID. I would also confirm that:

• the DEV workspace is still assigned to an active Fabric capacity
• you are reconnecting it as a workspace Admin

Microsoft's Git integration process requires an Admin for connection management.

I wouldn't assume the folders or unsupported item types are the cause just from the screenshot. Fabric can connect workspaces containing unsupported items and normally ignores them for Git.

If the detailed error is still generic and the same branch continues to initialize successfully in another workspace, I would raise a support ticket with the workspace ID, request ID and timestamp. At that point you have a strong indication that the issue is specific to the DEV workspace rather than the Git branch itself.