Issue publishing live connected reports

[awin_w]

I'm getting some strange new behavior trying to publish new versions of reports connected to a fabric directlake semantic model. I'll publish it; confirm at the prompt asking if I want to replace the existing report; then instead of getting the usual 'success' prompt I get the "your file was published, but disconnected" prompt implying I have a datasource refresh issue I need to go configure my dataset to fix.

So that might be fine if that's what was going on. Except in these cases, these are live reports on directlake semantic models. The dataset is fine and when I go to check the newly published report in the service the changes on the new visuals have not actually been successfully published. Trying to troubleshoot and following the link in the prompt to "open dataset setttings" goes nowhere in this instance. I have manually refreshed the semantic model and tried changing its data source connection, neither had any effect. This is all very odd and has just cropped up today. I actually experienced it where I successfully published a version, had to make another visual change later in the day and attempted to publish again and now am encountering this issue it every time. The semantic model involved is in a separate workspace from the report but both are on the same capacity this has not happened before.

[Poojara_D12]

Hi @awin_w 

The issue you're encountering—"Your file was published, but disconnected"—when trying to republish a report connected to a Fabric DirectLake semantic model, suggests a publishing pipeline hiccup in Power BI Service that may be related to how report-to-semantic model bindings are handled across workspaces. In typical DirectLake scenarios, the semantic model doesn’t require refreshes since it reads directly from the delta table, so the message about needing to manually refresh the semantic model is misleading. What seems to be happening here is that during the publishing step, Power BI fails to rebind the report to the existing semantic model correctly, especially when the model lives in a different workspace than the report. While this setup (report and dataset in separate workspaces but same capacity) generally works, recent backend changes in the Power BI Service or Fabric platform may be causing temporary disruptions to this cross-workspace linkage.

Even though the publishing prompt shows completion, the report doesn't actually update in the service, and the new visuals don't reflect. Furthermore, the "Open dataset settings" button is non-functional, likely because the system is trying to reference a dataset that is already external to the report's workspace. This is consistent with behaviors reported by other users where cross-workspace connections or external semantic models (especially DirectLake ones) become unstable temporarily. Since you've already verified that the semantic model is healthy and refreshed, the issue lies not with the dataset itself but with how the deployment or metadata binding step fails silently.

To work around this, consider these steps: (1) use "Get Data > Power BI datasets" in Power BI Desktop to reconnect to the live semantic model before publishing again, ensuring it's recognized properly; (2) test publishing the report into the same workspace as the semantic model to isolate the issue; and (3) clear out any cached connection metadata in Desktop and try publishing fresh (File > Options > Clear cache). If the issue persists, it’s best to raise a ticket with Microsoft support, as this may be a regression in the publishing pipeline tied to recent Fabric changes.