Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Special holiday offer! You and a friend can attend FabCon with a BOGO code. Supplies are limited. Register now.
I created a new pipeline in a couple of iterations. In the first iteration, I had a single Copy task. Then, I added a bunch more tasks, saving each time, and executing/validating as I went. When I go into the Fabric workspace where the Pipeline lives, and click on the Pipeline to make changes, it is the stale version with just one task. If I go into the pipeline run history, I can see the successful later runs, and can even click on the last succesful run and see all the tasks I added. But from that view the only thing I can do is rerun, I can't save it, publish it or update it to the workspace. See 2 attached images, one of the workspace version of the pipeline, one of the "run history" version from a few hours later. I cannot find anywhere to "save" the version of the pipeline which is in run history, and don't know why the Workspace is still showing a stale version of the pipeline. Edited , more complete Pipeline visible in Run history
Pipeline I can edit from Workspace
@GraceGu Did you ever get any feedback or resolution on this? I'm looking at it from the other perspective where I have multiple engineers working on the same pipelines. I have done changes but if I save now will those changes be effective for everyone or only in my context. Would I then need to commit to make thos e changes live for everyone or is that just commit for the source control repo submission?
Would you mind filling a support case for this? We'll need engineering to track this one down. Thank you!