Forum Discussion
Power BI Workspace Source Control is Broken Again
1. Changes does not open.
2. Unclear what the conflicts are as there weren't this many changes.
3. Did not happen on other workspaces that are synced to the same repo.
4. When we click 'Update All' this is what shows up:
Tried to use the API to update the workspace, and this is the error I got - BUT IT WORKED:
Error details: {
"requestId": "9dd3f165-4510-4950-a736-da4ab6af6da6",
"errorCode": "WorkspaceHeadMismatch",
"message": "The workspace head does not match the current head."
}
Hey noahfox ,
Thanks for sharing the detailed screenshots it looks like you're running into a known hiccup that started appearing recently after Microsoft introduced folder support for Git in Fabric. Fabric now reflects folder structures in Git, which can unexpectedly trigger a large number of false change/conflict detections, especially if you didn't make any recent manual updates. That’s probably because of,
- You’re seeing 66 changes / 98 updates suddenly.
- The system shows 52 conflicts, even though you didn't touch those items.
- Clicking “Update All” shows a blank screen this seems to be a UI bug when the system can’t fully render large or malformed diffs.
- Avoid “Update All” until you review changes
Since it’s blank, it’s risky especially if you’re unsure what those changes are.
- Use the API or Git CLI to check what's changed
You can compare your workspace’s current Git head vs the repo head to see if the structure change is causing the mismatch.
- If using the Power BI REST API, look out for this json.
{
"errorCode": "WorkspaceHeadMismatch",
"message": "The workspace head does not match the current head."
}That error means your workspace is out of sync with Git which fits the situation. Interestingly, in your case the update still succeeded, so it seems the backend accepted it after a force.
- Workaround if things remain broken
- Export your artifacts (PBIX, datasets, etc.)
- Disconnect Git from the workspace
- Reconnect and resync to start fresh from the Git branch
Also check whether any recent Fabric commits in the Git repo added .folders or changed file paths that’s often the root of these surprise sync issues.
Regards,
Akhil.
7 Replies
Sorry I have no clue what you're saying
The issue is caused by local metadata mismatch in this specific workspace due to the new Fabric folder Git support.
- Changes not opening – UI bug triggered by unresolved conflicts.
- Too many conflicts – Likely due to previously untracked folder or system changes now detected by Git.
- Other workspaces fine – They didn’t have local changes or outdated metadata, so no conflict was raised.
Try,
- Manually pull latest from Git or reset local state.
- Use Git tools to view and resolve the 52 conflicts.
- Avoid Update All until resolved.
- Refresh Source Control after that.
Hey noahfox ,
Thanks for sharing the detailed screenshots it looks like you're running into a known hiccup that started appearing recently after Microsoft introduced folder support for Git in Fabric. Fabric now reflects folder structures in Git, which can unexpectedly trigger a large number of false change/conflict detections, especially if you didn't make any recent manual updates. That’s probably because of,
- You’re seeing 66 changes / 98 updates suddenly.
- The system shows 52 conflicts, even though you didn't touch those items.
- Clicking “Update All” shows a blank screen this seems to be a UI bug when the system can’t fully render large or malformed diffs.
- Avoid “Update All” until you review changes
Since it’s blank, it’s risky especially if you’re unsure what those changes are.
- Use the API or Git CLI to check what's changed
You can compare your workspace’s current Git head vs the repo head to see if the structure change is causing the mismatch.
- If using the Power BI REST API, look out for this json.
{
"errorCode": "WorkspaceHeadMismatch",
"message": "The workspace head does not match the current head."
}That error means your workspace is out of sync with Git which fits the situation. Interestingly, in your case the update still succeeded, so it seems the backend accepted it after a force.
- Workaround if things remain broken
- Export your artifacts (PBIX, datasets, etc.)
- Disconnect Git from the workspace
- Reconnect and resync to start fresh from the Git branch
Also check whether any recent Fabric commits in the Git repo added .folders or changed file paths that’s often the root of these surprise sync issues.
Regards,
Akhil.Hi noahfox ,
Just checking in were you able to review the changes or try the workaround (export, disconnect Git, and reconnect)? The recent folder support in Fabric has been causing unexpected sync issues like this, so let me know if you’re still seeing conflicts or blank screens. Happy to help troubleshoot further if needed.
Thanks,
Akhil.Hi noahfox,
Were you able to try the export → disconnect Git → reconnect steps? Just checking if that resolved the sync issue or if you’re still running into it.
Regards,
Akhil.Hi noahfox ,
I hope the response provided helped in resolving the issue. If you still have any questions, please let us know we are happy to address.
Regards,
Akhil.
