Forum Discussion
Git sync with Workspace error - the items in the following list have a reserved name
The notebooks were deleted, and now I’m trying to sync them back from the repository, but it’s not working.
I’m getting the following error:
“Failed to complete request
We couldn't complete this request because the items in the following list have a reserved name. Try again later.”
I’ve already waited for about an hour, but the issue still persists.
Hi BorArt,
That's interesting, I've not encounted this issue before.
Are you using GItHub or DevOps? It shouldn't matter but maybe we can narrow down the scope and get to the bottom of this.
Have you tried "branching out" to a new workspace. Instead of creating a new workspace and connecting it to git, from the git menu in the original workspace you can branch out which will both create a new branch on the repo and create a new workspace connected to that branch.
11 Replies
- tayloramy
Super User
Hi BorArt,
That's interesting, I've not encounted this issue before.
Are you using GItHub or DevOps? It shouldn't matter but maybe we can narrow down the scope and get to the bottom of this.
Have you tried "branching out" to a new workspace. Instead of creating a new workspace and connecting it to git, from the git menu in the original workspace you can branch out which will both create a new branch on the repo and create a new workspace connected to that branch.
I’m using GitHub and I managed to narrow the issue down.
I was switching between branches with different content:
- Branch main → contains notebook_1
- Branch dev → contains notebook_1 and notebook_2
When I tried to switch back from main to dev, I got the error:
“the items in the following list have a reserved name.”Then I tried pulling the same repo into a newly created workspace — and hit the same issue.
Next, I used a deployment pipeline to move the items into another new workspace (not the corrupted one). That worked. After that, I connected the Git repository to this new workspace, and now I can switch between branches with different item sets without any problems. It also started working again in the original workspace.
So at the moment, the issue is gone, but the workaround feels quite strange.However, I still cannot pull the repository into a completely empty workspace.
>> However, I still cannot pull the repository into a completely empty workspace.
It fixes if I create a deployment pipeline to a workspace.Even then I can remove the deployment pipeline, but this issue does not appear again"branching out" to a new workspace is also working
I tried to create a new workspace, but pull of the existing repository also is not working.
The same error - the items in the following list have a reserved name
But it is weird - workspace is completely new and there were not any objects yetSame issue here. Did you find solution?
Murtaza_GhafoorWhy is this happening ?
When a notebook or pipeline deleted from the workspace, but internal metadata or soft delete reference still exist in the workspace“the items of following have a reserved name”
Workaround:- Rename the notebook in the repository and reconnecting Git resolves the issue because Fabric treats it as a new thing instead of restoring the deleted notebook.
If this helps, ✓ Mark as Kudos | Mark as Solution| Help Others
No, it does not work
I changed "displayName": "name_v2",And folder name for this notebook
And I still see the same issue
- Rename the notebook in the repository and reconnecting Git resolves the issue because Fabric treats it as a new thing instead of restoring the deleted notebook.
It seems that I can not pull the same notebook if it was already created in other workpsace
How to resolve this kind of issues?- tayloramy
Hi BorArt,
Very facinating.
Are you able to replicate this?
If you start a brand new workspace with a brand new repo, and do the same thing does it break?
If you can replicate it, then this is likely an edge case bug that needs to be addressed. Let me know if you are able to replicate it or not and I can see about poking some people and submitting a formal bug report.
