Forum Discussion
Investigate ‘Failure’ actions
The screenshot from the metrics app shows that this is an interactive operation called "Query" on a Dataset. The title of the visual says "Interactive operations for timerange".
https://learn.microsoft.com/en-us/fabric/enterprise/fabric-operations
I couldn't find the word "dataset" in the list of operations in the link above. Perhaps the operation shown in the screenshot is the same as "Interactive query" on a semantic model?
Is this a Direct Lake or Import Mode (or DirectQuery) semantic model?
Here are some ideas for finding out which queries failed:
- Find out which user triggered the failed queries, and ask them if they got any error message.
- You could try using the report yourself and see if any visuals fail.
- You can also open the report in Power BI Desktop and run performance analyzer on each report page. Then you will find out which queries are slow to load (performance issues).
- Perhaps it's possible to use Azure Log Analytics to find information about failed queries (although I haven't tried it personally).
-----------
On a side note: rescheduling background operations would probably not help much even if the issue was related to background operations. As background operations are smoothed over a 24 hour period, it shouldn't matter much about the specific time the operation gets triggered. Instead, reducing the number of refreshes within a 24-hour period would help to reduce the utilization (if background operations were the main issue here).
However, in this case we are looking at interactive operations (ref. the screenshot), not background operations. So background operations are not directly relevant for this case anyway.
Hi frithjof_v
Thank you for highlighting the areas I missed and correcting my mistakes.
The Metrics app still uses the old term "dataset" rather than the new term "semantic model". I think you are correct that the operation is the same as "Interactive query" on a semantic model.
As the status is "Failure" not "Rejected"/"Delayed", and their throttling time is 0s, does that mean it's more likely to be an issue with query timeouts or query data volume over limits? Maybe the cause is more related to the semantic model and the Power BI report? Of course, in the case of DirectQuery/LiveConnect, may also need to consider the impact of data sources and networks.
Best Regards,
Jing