Forum Discussion
Power Bi Service Refresh - timeout expiration issue
I'm having this issue in the Power BI Service (not desktop) when attempting to configure a new datasource. There are no options to manually set a timeout, and the default seems to error out after about 60 seconds.
How do we get around this?
Just ensure that you have configured the timeout settings on the data source. As well as that data starts getting returned as quickly as possible
- Anonymous7 years agoNot applicable
I am looking for some help here based on some issues I have been facing.
My dataset refresh fails once it goes beyond 5 hours. So does this mean that no refresh can run longer than 5 hours in Power BI service? Or does have to do with individual queries in Power BI?
So, hypothetically, lets say I have 50 queries in my dataset and each will run for exact 10 mins which makes it 8+ hours. Will this run fine or will it fail because total time taken is more than 5 hours?
FYI, of course I am talking about premium workspaces as I mentioned 5 hours.
Thanks for your help.
Regards
- GilbertQ7 years agoSuper UserHi there
What could possibly be happening is when using Power Premium there could be a lot of factors causing it to fail.
Such as running out of memory, other reports being loaded which could possibly stop the refresh and other things.
What I would suggest doing is to rather see how you can get the refresh time down by using incremental refreshing. That is where I would focus my effort.
When refreshing data there are quite a few moving parts which could affect the refresh failing. - Anonymous7 years agoNot applicable
I am in process of configuring Incremental for my report.
But my concern is - how will the first full refresh work considering my dataset takes 5+ hours for the full refresh?
Regards
- GilbertQ7 years agoSuper UserHi there
What if you had to initially change your incremental refresh to not go back with all your data, but a smaller dataset to see if that would help? - Anonymous7 years agoNot applicable
I can try with smaller dataset by using only few months of data.
But once I use all the months again, my dataset refresh time will increase and it will hit the timeout issue again.
Regards
- GilbertQ7 years agoSuper UserHi there
That would indicate that due to the data size something is causing an issue.
Have you had a look at the Power BI Premium Capacity App to see if you run out of allocated memory during the dataset refresh? - Anonymous7 years agoNot applicable
Hi All,
I am experiencing this time out issue now. its a import dataset and i dont see any duration parameter coded in the advance editor. do we need to add it to the code. also this issue is occuring suddenly.
- GilbertQ7 years agoSuper UserHi there
what do you mean by the duration parameter? - Anonymous7 years agoNot applicable
I mean the time out parameter that you set while connecting to any source. You can see that in advance editor M code.
[Timeout=#duration(0, 0, 5, 0)])
- Anonymous7 years agoNot applicableI guess the timeout parameter can only be set if using SQL Server. But not sure if that will override the 5 hours timeout which is present on Power BI Service for any individual running query. Regards
- Anonymous7 years agoNot applicableAlso, I have got this confirmation from Microsoft team that there is a limit on query timeout of 5 hours. Since I was using SAP HANA DB and there is a query which runs for 10+ hours. It runs fine on Desktop, but fails on Service due to this timeout issue. Regards
- GilbertQ7 years agoSuper UserHi there
That is correct, you have to make sure it finishes within the 5 hours to get it refreshing. - Anonymous4 years agoNot applicable
In your query source settings there's an option to specify a timeout that is longer than the default one. But it looks as though even doing that would not solve the problem a lot of people in this thread seem to be having because Power BI simply cannot handle such large sets.
I do find it surprising that in the age of "Big Data" things like this haven't been resolved. Just an hour so ago Excel completely fell over when I passed just 500K rows to it