Forum Discussion
Semantic Model refresh disabled - report in different workspace
Hi cwollett
aj1973 Thanks for the inputs.
I hope the information provided by user was helpful. If you still have questions, please don't hesitate to reach out to the community.
- cwollett1 year agoAdvocate II
Hi v-priyankata
Unfortunately the information provided is not a solution.
- aj1973 mentioned that it is common to have semantic models and reports in separate workspaces
- When we do this, our underlying semantic models do not refresh
- The only error message we get is "due to inactivity" - which does not make sense as there are reports being used on top of the data model within the 60 day window.
- v-priyankata1 year agoCommunity Support
Hi cwollett
After two months of inactivity, scheduled refresh on your semantic model is paused. A semantic model is considered inactive when no user has visited any dashboard or report built on the semantic model. To resume scheduled refresh, revisit any dashboard or report built on the semantic model. That's why your scheduled refresh has been paused.
Thanks.- cwollett1 year agoAdvocate II
I understand this. However, we did not have two months of inactivity.
I have a semantic model of our incoming ticket requests. When I look at the lineage view and click "Show impact across workspaces" I see "2 Items impacted in total" - 1 is the semantic model in question, and the other is a report in another workspace.
When I check the usage tracking metrics, I see view report items throughout June and July on the report. Yet, it disabled the semantic model refresh.