Status:
New
Dataset schedule refresh fails intermittently.
Hi Team, I have one Power BI Dataset which is connected to the Azure Database. I have scheduled refresh for five times a day. Out of five times, it works 3 times but fails two times. If I try to ...
I had this issue too. Here's my solution to fix it.
It is probably too late a response for you given the date of your post but might help others.
I initially thought that the timeout refered to connection timeout, not command timeout.
I connected a dataflow to a serverless SQL server and found that if the connection request is made whilst the sql server is idle, then the startup time for sql is too long and nothing comes back to the requestor within the standard 30 second connection timout. At least, nothing useful comes back.
I added an option to the connection to include a long timeout. e.g. 2 or more minutes
Source = Sql.Database(server, database, [ConnectionTimeout=#duration(0, 0, 2, 0)])but this didn't fix the issue.
In my case, the request to refresh the dataflow will be triggered by a .net application, so I am ableto check in the application for a failure and retry if I get an Exception.
This doesn't help you though if you ae using another language / process for automating your refreshes.
What I conclude though is, you will have to handle the issue in the process that triggers the refresh, as it doesn't look like you can do anything in Power BI to handle it.
So the main point of this comment, is to say that neither altering the connection timeout in the connection string nor the command timeout in the query, will fix the problem 😞
In my case, the request to refresh the dataflow will be triggered by a .net application, so I am ableto check in the application for a failure and retry if I get an Exception.
This doesn't help you though if you ae using another language / process for automating your refreshes.
What I conclude though is, you will have to handle the issue in the process that triggers the refresh, as it doesn't look like you can do anything in Power BI to handle it.
So the main point of this comment, is to say that neither altering the connection timeout in the connection string nor the command timeout in the query, will fix the problem 😞