Set Semantic Model Refresh Timeout Limit

Hi Rob92

I don't believe such an option exists.

However, you could create your own leightweight monitoring and timeout setup, by leveraging the Power BI APIs.

The following API allows you to get the status of your refreshes: Datasets - Get Refresh History - REST API (Power BI Power BI REST APIs) | Microsoft Learn

The following API allows you to cancel an active refresh: Datasets - Cancel Refresh - REST API (Power BI Power BI REST APIs) | Microsoft Learn

_____________________________________________________
I hope my comment was helpful.
If your question was answered, please mark your post as 'Solved' and consider giving me a 'Thumbs Up'.
Find me on LinkedIn, Sessionize, or my blog Downhill Data

Hello,Jonvoge .

thanks for your concern about this issue.

Your answer is excellent!
Hi,Rob92 .I am glad to help you.
In fact, Jonvoge has already made a good suggestion: utilize the Power BI API to set up a refresh supervision to deal with refresh timeout situations in a timely manner.
Here are some additional suggestions I hope you find helpful:
1.Try to start with power BI reports, such as optimizing report models
Complex relationships and inefficient queries will slow down the refresh speed, you see also try to check and optimize your query logic and data model. Reduce some unnecessary operations.
URL:
Optimization guide for Power BI - Power BI | Microsoft Learn

2. If your report supports incremental refreshes (the Data source supports query collapses and there are Data/Time type fields in the data set for partitioning processing), you can configure incremental refreshes to reduce the amount of data that needs to be processed with each refresh.
5. Use XMLA endpoints (for Premium workspaces, Premium Per User)
XMLA endpoints allow you to implement semantic models that manage your reports in different ways
In this way, data can be customized, monitored, and managed. In this way, the refreshing is not affected by the maximum daily refreshing times (scheduled refreshing times and scheduled refreshing timeout) of the license, and works with RestAPI to improve the refreshing efficiency.
URL:
Advanced incremental refresh and real-time data with the XMLA endpoint in Power BI - Power BI | Microsoft Learn
The Evolution of XMLA Endpoint in Power BI: A Comprehensive Guide (insightsarena.com)
Announcing refresh history updates for models utilizing XMLA endpoints | Microsoft Power BI Blog | Microsoft Power BI
Power BI XMLA Endpoint - Step by Step Examples, How to Use? (excelmojo.com)

I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.

Best Regards,

Carson Jian,

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

First of all, there are a couple of different timeouts that are relevant to refreshes. I wrote a series of blog posts on refresh timeouts here:

https://blog.crossjoin.co.uk/2021/12/05/troubleshooting-power-bi-timeouts-part-1-the-two-five-hour-import-refresh-limit/

https://blog.crossjoin.co.uk/2021/12/12/troubleshooting-power-bi-timeouts-part-2-timeouts-specified-in-power-query-functions/

https://blog.crossjoin.co.uk/2021/12/16/troubleshooting-power-bi-timeouts-part-3-the-external-command-timeout/

The easiest option is probably (depending on the data source you're using) to set a timeout inside Power Query (as discussed in the second post) for the largest/slowest tables. You can set timeouts on refresh operations if kick them off using XMLA commands but that's quite hard to do.

If you use the Enhanced Refresh API you can control the number of retries. Probably the easiest way to use the Enhanced Refresh API to run refreshes is to use Semantic Link and the refresh_dataset method, something I show how to do in this blog post https://blog.crossjoin.co.uk/2024/05/12/the-partialbatch-commit-mode-in-the-power-bi-enhanced-refresh-api/