Forum Discussion
Committing models and experiments issue with sync from Git
Since the end of August 2025 Microsoft has silently added Git support for model and experiment items. Today we ran into the problem that we had a workspace with uncommitted models and experiments and we were unable to switch branches because of this. So we committed these items to the branch to be able to switch. As the new branch had none of these items, all the items were deleted from the workspace.
Afterwards we wanted to switch back to the branch with the models and experiments, but when syncing the workspace we ran into an undefined error. Also creating a new workspace and syncing this branch did not solve the problem. So, it looks like committing models and experiments breaks the sync from Git. We submitted a support ticket with request ID 2509031420001462 if you are running into the same problem.
If you agree with the option that we should be able to ignore Fabric items from being committed to Fabric, please read this article Git Integration for ML Models & Experiments – Support the Git Ignore Idea (in general) and upvote the ability for Git ignore here https://community.fabric.microsoft.com/t5/Fabric-Ideas/Git-Ignore-option-for-Source-Control/idi-p/4615128.
This problem has been solved by Microsoft on 17-9-2025 in the North Europe region.
6 Replies
This problem has been solved by Microsoft on 17-9-2025 in the North Europe region.
Hi nielsvdc
This issue happens because Git support in Fabric doesn’t fully handle model and experiment items yet. When you commit them, Git sees that the new branch doesn’t have those items and removes them from the workspace. That’s why sync fails or the items disappear. For now, the best approach is to avoid committing models/experiments into Git until Microsoft provides better support. You already did the right thing by raising a support ticket. I’d also suggest upvoting the Git Ignore idea shared in the community so Microsoft can prioritize it. This way, others facing the same problem will have a clear path forward.
Hi nielsvdc ,
Thanks for reaching out to the Microsoft fabric community forum.
Thanks for your prompt response
nielsvdc ,
I wanted to follow up and confirm whether you’ve had the opportunity to review the information provided by rohit1991 . If you have any questions or need further clarification, please don’t hesitate to reach out.
We appreciate your collaboration and support!
Best regards,
Lakshmi.If these items are not committed, switching branches within the workspace is not possible. Such workspaces currently contains lakehouses with data, as well as models and experiments. Creating a new workspace for each new branch requires first adding data to the lakehouses and recreating the models and experiments before development can resume. Initializing a new workspace with all necessary data typically takes approximately 4 hours before development in a different branch can begin. This process is highly insufficient.
If the Git support for models and experiments was released unintentionally and complete functionality is not yet available, consideration should be given to rolling back the feature as soon as possible. This issue is currently being investigated.
Hi nielsvdc ,
Thanks for the update. I agreethis setup makes branch-based development really hard. Rebuilding lakehouses and models every time takes too long, and the Git support feels incomplete. If the feature isn’t ready, rolling it back or marking it as preview would help.
Since you’ve already raised a support ticket, we’ll keep this thread open so that other users facing a similar issue can upvote the idea you suggested.
Git Ignore option for Source Control - Microsoft Fabric Community
We truly appreciate your continued engagement and thank you for being an active and valued member of the community.
Best Regards,
Lakshmi
