Forum Discussion
Semantic Model refresh disabled - report in different workspace
Hi cwollett
Technically this could be a bug in the dataset or more likely a failure as shown in here
Maybe, before rerunning the refresh in the service it is wiser to open the Power Query of the dataset in the Desktop to identify where the failure is coming from.
Thank you for your reply. We are definitely having the issue shown in the first note from your screenshot, not the second. Reasoning:
- There are no errors in either the semantic model or the report - I verified this by opening the PBIX of both and they refresh with no errors.
- Both the semantic model and the report have been refreshing for months with zero issues - so we are not disabled due to consecutive failures.
- The message we received over the weekend was that inactivity alone was the cause of the refresh being disabled.
The only reason I can think that this would be happening is that the report that gets visited is in another workspace. So if I visit the report, it doesn't know to kick off the refresh of the model in the other workspace? It didn't, by the way, I visited the report and it did not kick off the refresh despite the note in the screenshot saying to resume, visit a report built on the model.
Separating reports from its dataset in 2 different Wrokspaces is a healthy move according to Power BI best practices. A thin report is connected to its Dataset in a Live Connection Mode and the Queries are sent to the dataset as its data source and nothing else therefore visiting the report does not kick off the refresh of the dataset unless the dataset is in a DQ mode(which is not your case).
The messages from Power BI service can sometimes be confusing and you will have to troubleshooting yourself.