"File Published but Disconnected” Error When Publishing Power BI Report

[mati_gouda]

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:

1. Published a blank PBIX file → same “disconnected” result

2. Deleted the dataset/report in the service and re-published

3. Cleared Power BI Desktop cache

4. Refreshed the model locally in Desktop—works fine there

5. Re-entered credentials for SharePoint and dataflow connections

6. Recreated the pseudo-gateways/connections in the service

how to fix this?

[lbendlin]

"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.

[mati_gouda]

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. 

[lbendlin]

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).

[mati_gouda]

same thing. Had done it previously and did it again just few minutes ago and still the same message

[v-sshirivolu]

Hi @mati_gouda,

Thanks for reaching out to the Microsoft fabric community forum.

Try These -

Upgrade connectors

Switch from legacy Gen1 dataflows to Gen2 or standard cloud connectors.

Ensure you’re not blocked by permissions when doing this.

Configure/update a gateway

If your model includes on-premises or mixed-source connections, you need a standard on-premises data gateway (personal gateway won't suffice for composite/direct query models).

After publishing, go to the dataset’s workspace - Settings- Gateway connection, and map each data source to the gateway

Validate Data Source Credentials

In the service, under Data source credentials, re-enter and confirm all OAuth2 credentials (SharePoint, dataflows, etc.)

Re-publish the PBIX

After making these changes, republish. The "disconnected" banner should disappear, and the dataset will resume scheduled and on-demand refresh.

If the response has addressed your query, please Accept it as a solution and give a 'Kudos' so other members can easily find it

Best Regards,
Sreeteja.
Community Support Team 

[mati_gouda]

Hello,

upgrade connectors - As you see I'm already using proper Dataflow connectors. Which are Gen2 connectors? Are there any different connectors that I'm already using? 

 Configure/update a gateway - it's already done. Same thing.

Validate Data Source Credentials - validated, still same issue

Re-publish the PBIX - does not help. The report is refreshing but does not want to refresh when publishing. 

[v-sshirivolu]

Hi  @mati_gouda ,

That “File published, but disconnected” message usually means Power BI couldn’t match the data sources in your PBIX file with the ones already set up in the service. It’s a common issue, and luckily easy to fix. After publishing, go to the workspace where your report is, open the dataset settings, and check the “Gateway and cloud connections” section. There, make sure each data source is properly mapped. For cloud sources like SharePoint or Fabric Dataflows, you might need to click “Recreate cloud data sources” if any of them look blank or broken. If you’re using on-prem data, double-check that it’s linked to the right gateway. Once everything’s mapped, hit Apply and try a manual refresh. If that works, you can set up your scheduled refresh again and the disconnected message should go away.

If the response has addressed your query, please Accept it as a solution and give a 'Kudos' so other members can easily find it

Best Regards,
Sreeteja.
Community Support Team 

[mati_gouda · Accepted solution]

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?

[lbendlin]

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?

That sounds like a serious bug.  If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .

[mati_gouda]

Hello,

I have pro license, I've submitted a ticket via power platform admin. I will update the thread when it's going to be fixed or something like that. Thank you for your help

[mati_gouda]

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.