Forum Discussion
Dataflow Timeout
Hi all,
Anyone know a way to stop the dataflow timing out.
Datasource is on-prem SQL database, using a native query. Result set is in the millions
Thanks
Mike
Hi Mike,
Please send to our support email the screenshot with the failure you got, so we can investigate further.
Thanks,
Galia
17 Replies
Can anyone share the solution to this? Not sure the marked solution is actually a solution
I have no solution for the problem, but did use the following workaround.
I created the desired query in PowerBI Desktop. Then I captured the M code from the advanced editor and pasted it into the editor in Dataflows. Then I just clicked 'Close and Save' and navigated away without waiting for the preview to finish.
The dataflow loaded without problem, but managing the query has to be done out of Power Query Editor, and then copied into the editor in the Dataflows interface.
Not a very satisfying approach, but it is functional.
- Thanks for reply. I take that approach with every entity I build, create in desktop then lift and shift the query from advanced editor.
Interestingly I tried to save my entity again after-hours and it worked a treat, so guessing some kind of memory/capacity thing?
I work for a global company and I'm based in UK I was trying to get this done at 2pm today, just as our friends across the pond come online. I had success at 6pm
I have the same issue, I have been searching for a solution for the past week.
When trying to refresh a dataflow of small size it is always succesful, but when the size gets bigger it fails in 4 or 6 minutes ( exactly) which makes me think it is a timeout setting.
I don't know where to address this issue and get an actual answer.
Same issue here.... if I paste M code from advanced editor, sometimes it works when I save & close, and sometimes it still fails saying i have a query error. The error is that the query timed out.
What is the solution to this?
The default timeout on the SQL Connector is 10 minutes but there is a parameter in the connector's config where you can specify a longer duration. Here's an example setting the timeout on the command to 30 minutes:
Sql.Database("server", "database", [CommandTimeout = #duration(0, 0, 30, 0)])Anonymous,
Please refer to below:
There are a few known limitations to using Enterprise Gateways and dataflows:
- Each dataflow may use only one gateway. As such, all queries should be configured using the same gateway.
- Changing the gateway impact the entire dataflow.
- If several gateways are needed, the best practice is to build several dataflows (one for each gateway) and use the compute or entity reference capabilities to unify the data.
- Dataflows are only supported using enterprise gateways. Personal gateways will not be available for selection in the drop down lists and settings screens.
Community Support Team _ Jimmy Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi Mike,
Can you please share the refresh log (by downloading the CSV file from the refresh history)?
Please mail it to dataflow support DL: [email protected]
Thanks,
Galia
Not sure if anyone is still concern about this; but you can split the whole datatable in SQL into multiple segments; then the oldest data is loaded overnight one by one. Then at the transforming phase, you can merge them all together using resource of Power BI service. That should work to bring in huge amount of data like you said.
