Fabric Notebook does not reflect CI/CD deployed changes and remains on a previous version despite successful synchronization

Question

Fabric Notebook does not reflect CI/CD deployed changes and remains on a previous version despite successful synchronization

Pinto, Michele 0

Products

Microsoft Fabric and Notebooks

Problem Description

We are experiencing an issue where a notebook updated through our CI/CD process does not reflect the newly deployed content in Microsoft Fabric.

The deployment completes successfully and the workspace reports a synchronized state. However, when the notebook is opened in the Fabric UI, an older version of the notebook is displayed.

To be precise, when the user opens the notebook, the Fabric UI shows the new version for a second and then immediately after it shows the old version, showing the message "Another user has saved changes to this notebook. Select View changes to see their changes and choose which version to keep."

The behavior is 100% reproducible.

Stack

Microsoft Fabric
Notebook artifact
GitHub repository
GitHub Actions CI/CD deployment
Fabric workspace connected to source control

Reproduction Steps

Open a notebook in the Fabric UI.
Create a new branch/worskspace
On the new branch/worskspace, modify the notebook in the GitHub repository
On the new branch/worskspace, commit the new version of the notebook
Deploy the updated notebook through the GitHub Actions CI/CD pipeline (merging a Pull Request)
Verify that the deployment completes successfully.
Open or refresh the notebook in Fabric.

Expected Result

The notebook should display the latest version that was deployed through the CI/CD pipeline.

Actual Result

The notebook continues to display a previous version of the content instead of the version deployed by the pipeline.

When the user opens the notebook, the Fabric UI shows the new version for a second and then immediately after it shows the old version, showing the message "Another user has saved changes to this notebook. Select View changes to see their changes and choose which version to keep."

Additional Info

No changes were made from the Fabric notebook editor during the test, it was only opened in the UI
The issue remains even after:
Clearing the browser cache
Closing and reopening the notebook
Redeploying the notebook
- Redeploying while the notebook remains closed
- Accessing with other credentials using another laptop
- The Source Control panel shows:
  - No changes to pull
    - No changes to push
      - No synchronization warnings
      - The workspace appears fully synchronized.
      - The issue is reproducible.

Impact

The notebook content visible in Fabric cannot be trusted to represent the version deployed through CI/CD. This creates uncertainty regarding which version of the notebook is actually being executed and complicates validation of deployments.

Questions

Is this a known issue with Fabric Notebooks and Git/CI-CD integration?
Are there known synchronization delays or notebook metadata issues that could cause an older notebook version to remain visible?
Is there a recommended method to verify the notebook definition currently stored in Fabric after deployment?

Pinto, Michele 0 Reputation points

2026-09-22T14:46:59.3833333+00:00
I can understand that a conflict may occur when a notebook is updated externally through Git or CI/CD, even though it is unclear why simply having the notebook open, without making any changes, can result in the deployed version being overwritten.

The more significant concern is that the conflict is completely invisible from the Source Control experience. After deployment, the Source Control panel reports:

No changes to pull

No changes to push

No synchronization warnings

Therefore, the workspace appears to be fully synchronized with Git. However, opening the notebook shows that it is actually different from the version stored in the repository and displays the message "Another user has saved changes to this notebook."

From a user perspective, this is problematic because the synchronization status cannot be trusted. If Fabric creates a local conflict state, I would expect that state to be reflected in the Source Control panel as pending changes, a warning, or some indication that the workspace is no longer aligned with Git.

Could you please clarify:

Is it expected that notebook conflicts are not reflected in the Source Control panel?

Why does the workspace report a fully synchronized state when the notebook content differs from the version in Git?

How can users reliably verify that the notebook version deployed through CI/CD is the version currently stored and displayed by Fabric?

The issue is not the existence of a conflict itself, but the fact that the workspace appears healthy and synchronized while the notebook content is not actually aligned with the repository.

Your answer

Pinto, Michele 0 Reputation points

2026-09-22T14:46:59.3833333+00:00

I can understand that a conflict may occur when a notebook is updated externally through Git or CI/CD, even though it is unclear why simply having the notebook open, without making any changes, can result in the deployed version being overwritten.

The more significant concern is that the conflict is completely invisible from the Source Control experience. After deployment, the Source Control panel reports:

No changes to pull

No changes to push

No synchronization warnings

Therefore, the workspace appears to be fully synchronized with Git. However, opening the notebook shows that it is actually different from the version stored in the repository and displays the message "Another user has saved changes to this notebook."

From a user perspective, this is problematic because the synchronization status cannot be trusted. If Fabric creates a local conflict state, I would expect that state to be reflected in the Source Control panel as pending changes, a warning, or some indication that the workspace is no longer aligned with Git.

Could you please clarify:

Is it expected that notebook conflicts are not reflected in the Source Control panel?

Why does the workspace report a fully synchronized state when the notebook content differs from the version in Git?

How can users reliably verify that the notebook version deployed through CI/CD is the version currently stored and displayed by Fabric?

The issue is not the existence of a conflict itself, but the fact that the workspace appears healthy and synchronized while the notebook content is not actually aligned with the repository.