Forum Discussion
Items deleted after renaming pipeline.
Hi all.
I have the following concern: I was working with a Fabric pipeline named "pipeline1". This pipeline has several ForEach activities and parameters where run some notebooks.
Then, I reorganized the folders where notebooks are located and also renamed the pipeline according to the function it ultimately has to perform.
Finally, when I wanted to run the pipeline again there was no activity within the pipeline. "pipeline2" (for ex) was left empty.
But, on the other hand, I'm able to see the "view run history".
Somebody knows if I can get my original pipeline back without relocate the notebooks?
And, also, I would like to know why this happens?
Thanks in advance!
Hi ArielSubia
What you're describing is a known (and quite frustrating) behavior in Microsoft Fabric Pipelines ,the same thing happened to me when I started; they put the folders on cloth. Let me explain what happened and how you can recover.
Why does this happen?
Activities inside a Fabric pipeline (ForEach, Notebook, etc.) store references to notebooks using their internal Object ID combined with the relative path within the workspace. When you reorganize the folders where notebooks live, those paths change — and the pipeline loses its references. The result: activities become orphaned or simply disappear from the canvas when you reopen the pipeline.
Renaming the pipeline itself shouldn't cause this, but folder reorganization does, consistently, in the current version of Fabric Pipelines.
Can I recover the original configuration?
Yes, you have a few options:
- Deployment Pipelines / Git Integration (if enabled): If your workspace was connected to a Git repo (Azure DevOps or GitHub), you can recover the pipeline JSON from commit history before the change. The pipeline .json file contains the full definition of activities, parameters, and connections.
- Run History as a reference: Since you can see the Run History, you can inspect previous executions to identify which notebooks ran and in what order. It won't restore the pipeline, but it gives you the exact map to rebuild it.
- Manual restoration from JSON: If you export the current and original pipeline (if you have a copy), you can edit the JSON directly and reassign the correct objectId values and notebook paths. Tedious, but it works.
- No Git, no prior copy: Unfortunately, Fabric doesn't have a native pipeline versioning system outside of Git Integration. In that case, manual reconstruction using Run History as a guide is the most viable path.
My Recommendation going forward:
Enable Git Integration in your workspace. It's the most effective safety net for exactly this kind of scenario — every save gives you a recoverable snapshot of the pipeline JSON.
If my comment helped solve your question, it would be great if you could like the comment and mark it as the accepted solution. It helps others with the same issue and also motivates me to keep contributing.
Thanks a lot, I really appreciate it.
3 Replies
- arabalca
Super User
Hi ArielSubia
What you're describing is a known (and quite frustrating) behavior in Microsoft Fabric Pipelines ,the same thing happened to me when I started; they put the folders on cloth. Let me explain what happened and how you can recover.
Why does this happen?
Activities inside a Fabric pipeline (ForEach, Notebook, etc.) store references to notebooks using their internal Object ID combined with the relative path within the workspace. When you reorganize the folders where notebooks live, those paths change — and the pipeline loses its references. The result: activities become orphaned or simply disappear from the canvas when you reopen the pipeline.
Renaming the pipeline itself shouldn't cause this, but folder reorganization does, consistently, in the current version of Fabric Pipelines.
Can I recover the original configuration?
Yes, you have a few options:
- Deployment Pipelines / Git Integration (if enabled): If your workspace was connected to a Git repo (Azure DevOps or GitHub), you can recover the pipeline JSON from commit history before the change. The pipeline .json file contains the full definition of activities, parameters, and connections.
- Run History as a reference: Since you can see the Run History, you can inspect previous executions to identify which notebooks ran and in what order. It won't restore the pipeline, but it gives you the exact map to rebuild it.
- Manual restoration from JSON: If you export the current and original pipeline (if you have a copy), you can edit the JSON directly and reassign the correct objectId values and notebook paths. Tedious, but it works.
- No Git, no prior copy: Unfortunately, Fabric doesn't have a native pipeline versioning system outside of Git Integration. In that case, manual reconstruction using Run History as a guide is the most viable path.
My Recommendation going forward:
Enable Git Integration in your workspace. It's the most effective safety net for exactly this kind of scenario — every save gives you a recoverable snapshot of the pipeline JSON.
If my comment helped solve your question, it would be great if you could like the comment and mark it as the accepted solution. It helps others with the same issue and also motivates me to keep contributing.
Thanks a lot, I really appreciate it.
Hi arabalca
I apologize for the delay in my response.
I'm going to describe what happened on my project. After a few hours, or even the next day (I'm not entirely sure) the pipeline was restored without making any changes to the canvas. It seems Fabric lasts some hours to restore any changes.
Finally, I ran the pipeline successfully. No changes were necessary.Thanks for taking the time to reply. I'm going to accept your solution.
Best regards!
v-aatheequeCommunity Support
Hi
We wanted to follow up to check if you’ve had an opportunity to review the previous responses. If you require further assistance, please don’t hesitate to let us know.
