Facing Git and Workspace Sync Issues

Hello Vedanth1111 

Thank you for sharing the detailed scenario and troubleshooting steps.

Based on the behavior observed, this appears to be related to an intermittent synchronization inconsistency between the Microsoft Fabric workspace and the connected Git branch, rather than an issue with the deployment process itself. Similar cases have been observed where the latest commits are successfully available in the repository, but certain artifacts, including pipelines, do not immediately appear or synchronize correctly within the workspace, even when sync operations complete without errors.

Since Fabric Git Integration relies on workspace-level metadata synchronization, temporary misalignment between the workspace and branch state can occasionally result in partial or outdated workspace visibility. The resolution you applied by creating a new feature branch and redeploying likely triggered a fresh synchronization and metadata reconciliation process, which explains why the pipelines became visible again.

To help reduce the likelihood of similar issues, it is recommended to keep the workspace synchronized with the latest branch state before validations or deployments, prefer incremental changes over large bulk updates, and use controlled feature branch workflows wherever possible.

If the issue recurs, capturing the Request ID or Activity ID and raising a Microsoft Support ticket would help with backend investigation, as these synchronization inconsistencies may not always be diagnosable from the UI alone.

For reference:

https://learn.microsoft.com/fabric/cicd/git-integration/intro-to-git-integration

https://learn.microsoft.com/fabric/get-started/known-issues/known-issues

Regards,

ABD