Forum Discussion
Fabric Pipeline stuck on Loading - pipeline editor does not open
Hi, I am facing an issue with Microsoft Fabric Data Pipelines. The pipeline editor remains stuck on Loading and the activities/canvas never appear. The issue happens in multiple workspaces in the same tenant. I also created a new pipeline in another Fabric trial workspace, but it has the same issue. Lakehouse is working normally, but Pipeline remains stuck on Loading. I have tried refreshing and reopening Fabric and testing in another workspace, but the issue persists. Is anyone else experiencing this issue? Could this be a Fabric service-side issue? I have attached screenshots showing the Loading screen. Thanks
Hi NaraayaPC
Thank you for providing the details and screenshots.
Based on the behavior described, since the Pipeline editor remains stuck on “Loading” across multiple workspaces, including a newly created pipeline in another Fabric trial workspace, this does not appear to be isolated to a specific pipeline or workspace.This could potentially indicate an issue with the Fabric Data Factory/Pipeline authoring experience or a service-side issue. However, we would need to verify the current Fabric service health and known issues before confirming this.
As the next troubleshooting steps, please try:
- Opening Fabric in an InPrivate/Incognito browser session.
- Testing with another browser (Edge/Chrome).
- Temporarily disabling browser extensions/ad blockers.
- If applicable, testing from a different network without VPN/proxy.
5 Replies
- v-csrikanth
Community Support
.
v-aatheequeHi NaraayaPC
Thank you for providing the details and screenshots.
Based on the behavior described, since the Pipeline editor remains stuck on “Loading” across multiple workspaces, including a newly created pipeline in another Fabric trial workspace, this does not appear to be isolated to a specific pipeline or workspace.This could potentially indicate an issue with the Fabric Data Factory/Pipeline authoring experience or a service-side issue. However, we would need to verify the current Fabric service health and known issues before confirming this.
As the next troubleshooting steps, please try:
- Opening Fabric in an InPrivate/Incognito browser session.
- Testing with another browser (Edge/Chrome).
- Temporarily disabling browser extensions/ad blockers.
- If applicable, testing from a different network without VPN/proxy.
NaraayaPC This looks more like a Fabric Pipeline authoring/service-side issue rather than a problem with a specific pipeline or workspace.
The key indicators are that:
- The Pipeline editor remains stuck on Loading.
- It happens across multiple workspaces in the same tenant.
- A newly created pipeline in a separate Fabric trial workspace has the same behavior.
- Other Fabric items such as the Lakehouse are working normally.
I would still recommend a quick check using an InPrivate/Incognito window, another browser, and temporarily disabling extensions/ad blockers. Also try from another network if possible. These are the standard checks Microsoft recommends for Pipeline authoring/loading issues.
However, if the issue reproduces across browsers, workspaces, and even a separate trial capacity, I would strongly suspect a Fabric service/authoring-layer incident rather than permissions, pipeline configuration, or capacity on a particular workspace.
I would check the Microsoft Fabric Service Health/known issues and, if the problem continues, raise a Microsoft support ticket with the Activity ID, tenant ID, workspace IDs, region, browser details, and timestamp.
There have been previous Fabric incidents where the Pipeline designer became unavailable or remained stuck loading, including cases related to the Fabric service or capacity layer.
So in this particular case, I wouldn't spend too much time recreating pipelines—the cross-workspace and cross-trial behavior is a strong indication that the problem is higher up in the Fabric service.
My take: if you have already tested different workspaces and a fresh trial pipeline, I would wait/check Fabric Service Health and raise a support ticket rather than repeatedly recreating pipelines.
- v-aatheeque
Hi NaraayaPC
Have you had a chance to look through the responses shared earlier? If anything is still unclear, we’ll be happy to provide additional support.
- v-aatheeque
Hi NaraayaPC
Following up to confirm if the earlier responses addressed your query. If not, please share your questions and we’ll assist further.
