Forum Discussion
Deployment Pipeline not loading
Has anyone encountered the issue where a Deployment Pipeline that was previously working fine, no longer pulls up anything? We have 3 DPs. 2 work fine, but 1 of them just says "Loading Pipeline" and never displays anything - not the stages nor the artifacts. Just the blank screen with the above message. if so, how was it resolved? This just started happening somewhere between Feb 8 and Feb 14 2024.
Here is the solution that worked for us. We used the Rest API to unattach our dev workspace from the DP. We then removed several objects (rpts / models / score cards) that were not needed. At least 2 of these used a more obscure Marketo data connection that may have been dropped as supported. (Not sure). So we are not sure if we had to reduce below a certain # objects or if removing the reports that had more obscure data connections solved it. But once we did, we could reassign this dev workspace to the DP and proceed as normal. Luckily we did not have to delete the whole pipeline and recreate it which is actually what MS said we should do.
Hi gkwright88 , Hi all,
The issue has been resolved by the product team and you can deploy and open pipeline to do so.Best regards,
Albert He
21 Replies
Hi gkwright88 , Hi all,
The issue has been resolved by the product team and you can deploy and open pipeline to do so.Best regards,
Albert He
Anonymous Can I find any official communication on this issue from Microsoft outside of this Community forum?
Hi gkwright88 ,
Based on your description, there are a few things you can do to troubleshoot if this is the cause of this problem:
1 A pipeline can run for a long time and then fail due to job time-out. Job timeout closely depends on the agent being used. Free Microsoft hosted agents have a max timeout of 60 minutes per job for a private repository and 360 minutes for a public repository.
2.If you're currently running other pipelines, you might not have any remaining parallel jobs, or you might have hit your free limits.
3Another reason maybe you don't have enough concurrency.4.Also, your pipeline might not move to the next stage because it's waiting on approval.
The above descriptions are just some of the possible causes of this problem, if you want to know more about the causes or the solutions to the corresponding causes, you can refer to the following documents:
Troubleshoot pipeline runs - Azure Pipelines | Microsoft Learn
Troubleshoot pipeline failure to start - Azure Pipelines | Microsoft Learn
Troubleshoot the Fabric lifecycle management tools. - Microsoft Fabric | Microsoft LearnBest regards,
Albert He
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly
I am also facing same issue - the deployment pipeline cannot be loaded. It remains stuck, displaying the message “Loading Pipeline…” when an attempt is made to open the Power BI deployment pipeline.
Hello everyone. I am also expiricing this. We only have one Deployment Pipeline and it has exactly the same behaviour now.
I can create more and those seem to work, unfortunately I don't have a solution yet.
Reply to MS support on 21-feb-2024
I’m reaching out to you regarding the loading screen issue you are facing with pipelines page, this is a known issue and impacting many other users, our engineering team shared an ETA for this to be fixed by middle of the next week, initial ETA is 27/2/2024
Too many reports to move to new pipelines, dependencies and parameters ...
Please keep us updatet on this issue, we experience the same. Hope Microsoft will fix this 27/2/24.
I must say that without changing anything the Deployment Pipeline is now working
That's good news for you. In my situation, we actually were on with microsoft support, and in Edge, developer tools recorded a trace and they are looking at it. Worst case will be that we need to delete the deploy pipeline and then create a new pipeline and re-add our dev, test,prod workspaces to it. We are waiting to see if the trace identifies anything else first though. I'll update the thread later with our final resolution.
My organization is facing this same issue with one of our largest pipelines. It was discovered this morning and is still not working. I do hope there is a solution outside of rebuilding the entire thing as that would be a time consuming endeavor.
The trace we did revealed nothing to MS. They have said we will need to detach the workspaces from the pipeline. Since you cannot go to the pipeline that is stuck to do that, they sent us a link to a REST API: https://learn.microsoft.com/en-us/rest/api/power-bi/pipelines/unassign-workspace which you can use the Try it feature, plug in your info and it should perform the task. We are going to then reattached each WS to the existing pipeline and see if that resets it. If not, we'll repeat and the 2nd time actually delete the pipeline and create it again, then attaching the WS's to it. Will report results later. Hopefully the first step works and saves us needing to create all the deployment rules again.
Hi gkwright88, Hi all,
We have reported this issue and submitted it to the product team.
They have been aware of the issue and the engineers will do their best to resolve it. I will update here if there is any progress, so please be patient.Best regards,
Albert He
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly
Here is the solution that worked for us. We used the Rest API to unattach our dev workspace from the DP. We then removed several objects (rpts / models / score cards) that were not needed. At least 2 of these used a more obscure Marketo data connection that may have been dropped as supported. (Not sure). So we are not sure if we had to reduce below a certain # objects or if removing the reports that had more obscure data connections solved it. But once we did, we could reassign this dev workspace to the DP and proceed as normal. Luckily we did not have to delete the whole pipeline and recreate it which is actually what MS said we should do.
I am facing the same issue right now, and we are also in contact with Microsoft Support. If I have any news from our side, I let you know.
I am assuming if you "Unassign" any workspace using API, it will remove all Deployment rules? We're dealing with this issue for 2 customers this week. One of them using Paginated reports.
I have also tried below but no luck so far
- "unassign" workspaces using API
- Delete Pipeline and created a new but the spinner wont go away
This is stopping our customers to make any promotions. I requested to raise the severity on this case, will keep you posted.
2
It appears that this issue has been rsolved. The DP opens up fine now and we're able to manage deployment.
