Forum Discussion
"File Published but Disconnected” Error When Publishing Power BI Report
I’m running into a frustrating issue where every time I publish my report to the Power BI service, I get a “File published, but disconnected” notification—and the report never actually refreshes online during publishing. I can refresh report but only later. Here’s what I know and what I’ve tried:
Published a blank PBIX file → same “disconnected” result
Deleted the dataset/report in the service and re-published
Cleared Power BI Desktop cache
Refreshed the model locally in Desktop—works fine there
Re-entered credentials for SharePoint and dataflow connections
Recreated the pseudo-gateways/connections in the service
how to fix this?
Hello, I've did exactly what you've mentioned in your post (I've wrote about it as well in my previous posts) and it did not help.
I'm not using on-prem, datasources were mapped and problem occured both on personal connector and other created specific for this issue.
I was able to resolve the issue the problem is how.
There was a Data Activator created on top of the report/app I was using. Removing Data Activator completely, get rid of this issue. Do you know why?
11 Replies
"Disconnected" is not an error. It is merely an advice that you need to complete additional steps if you want to refresh the semantic model in the Power BI service.
"PowerPlatform Dataflows" have been deprecated a long time ago. You may want to recreate them with a current DF Gen1, or the newer DF Gen2 if you are on Fabric.
Thanks for answer. I don't understand additional steps as merely a week ago there was no issue and nothing structural in data model was changed/added. So I disagree and I tend to name it as an error. It's not like I created some simple thing and book cannot refresh it. It's a huge app developed by a couple of people that worked flawlessly previously.
From what I understand Dataflow Gen1 is the current approach I'm using, depreciated has been PowerBI.Dataflow (which has legacy connector as well). But I don't quite understand what I should do here. There is zero chance to change whole architecture right now. Another thing is that I don't have privilage and credentials to do this so that's out of the equation.Dataflow gen2 is the one connected via lakehouse or what? Also this is how datasources looks on my end, as you see I'm using Fabric Dataflow, not PowerBi ones.
in my opinion it's an error. Most of the things related to the power bi is sometimes barely working (including this forum, it's my second reply that somehow dissapears). It's not small report that throws an error. It's a huge app developed by couple of people that worked flawlessly for the last couple of months and suddenly it's this thing while none new datasource has been added.
As far as I remember what I'm using is Dataflow Gen1. and I don't quite understand what I should do. I don't have credentials and privilages to change anything on the backend side. Gen2 is this thing with Lakehouse?
This is how datasources looks on my end. I do believe that PowerBi.Dataflow is depreciated, connector states "legacy" as well.
Go to the settings page of the semantic model and look at the Data Source Credentials section. Maybe the Sharepoint access token has expired and needs to be renewed. For good measure, reapply all credentials for all four connections (OAuth2).
