Issue Re-branching to Existing Workspace in Fabric – "Unable to complete action" Error

[AbhishekRama]

We’re encountering an issue while working with workspace branching in Fabric and would appreciate any insights. 

Setup: 

• We have a production workspace named 1-prod and a development workspace named 1-dev. 

• 1-prod is integrated with git and 1-dev is not 

• When we branch out into 1-dev from 1-prod we need to specify the branch name, then it will automatically be integrated with git 

Iteration 1: 

• We branched from 1-prod to 1-dev. 

• Selected "Override existing objects in workspace". 

• Used branch name: developiteration1. 

• At this point, 1-dev was empty, and all objects from 1-prod were successfully moved. 

Iteration 2: 

• We attempted to branch again from 1-prod to 1-dev. 

• Selected the same "Override existing objects in workspace" option. 

• Used a new branch name: developiteration2. 

Issue: We received the following error message: 

"Unable to complete action. There was an error while attempting to complete this action. Please try again later or contact support if the issue persists." 

Attached screenshot below

From our investigation, the issue appears to be isolated with the Warehouse SQL Endpoint. We are getting this error even though we specifically select to overwrite the objects in the target workspace when branching out. 

Looking for advice on this issue 

[Anonymous]

Hi @AbhishekRama ,
Could you please confirm if you've submitted this as an idea in the Ideas Forum? If so, sharing the link here would be helpful for other community members who may have similar feedback.
If we don’t hear back, we’ll go ahead and close this thread. For any further discussions or questions, please start a new thread in the Microsoft Fabric Community Forum we’ll be happy to assist.
Thank you for being part of the Microsoft Fabric Community.

[Anonymous]

Hi @AbhishekRama ,
Could you please confirm if you have raised an idea in ideas forum? If so,  it would be greatly appreciated if you could share your link  with the community. This would be helpful for other members who may encounter similar issues to upvote on it
Thank you for your understanding and assistance.

[AbhishekRama]

Hi @Anonymous 

Thanks for your input on this.
I actually forgot to mention in my original post that we did try manually deleting the warehouse, and that workaround does work.

However, we’re hoping to avoid manual deletion if possible. 

Would you happen to know of any alternative approaches or best practices that could help us resolve this without having to manually delete the warehouse each time?

Appreciate your help and any guidance you can share!

[Anonymous]

Hi @AbhishekRama ,
Thank you for confirming. As SQL Endpoints are closely linked to the workspace, the overwrite option may not reliably reset them when branching which is a known limitation. At this time, manual deletion remains the only effective workaround. Alternatively, you may use separate workspaces for each branch iteration to prevent this issue. 
Appreciate if you could share the feedback on Microsoft Fabric Ideas. Which would be open for the user community to upvote & comment on. This allows product teams to effectively prioritize your request.

Hope this helps.If so,consider accepting it as solution.

Thank you.

Regards,
Pallavi.

[Anonymous]

Hi @AbhishekRama ,
Thank you for reaching out to us on Microsoft Fabric Coomunity Forum!

As a workaround, we recommend manually deleting the Warehouse SQL Endpoint from the target workspace (1-dev) before initiating the new branch operation. Once deleted, you may retry the branching process from 1-prod to 1-dev using a new branch name with the override option. Please note that SQL Endpoints in Fabric are tightly coupled with the workspace and may not support multiple overwrites through Git operations at this time, though Microsoft is working to enhance Git integration across all artifact types.
Please refer the below document for more information:Get started with Git integration - Microsoft Fabric | Microsoft Learn

Hope this helps.If so,give us kudos and consider accepting it as solution.
Thank you.

Regards,
Pallavi.