Forum Discussion
Dataset Refresh Failing due to Timeout
HI Anonymous ,
Based on this document: Data refreshes must complete in less than 2 hours if it is not in premium node.
If you are using the Import mode, th loading time depens on the size of your model (rows and columns), network status between pc and datasource, and also the performance of pc which runs the power bi. At last, calculated columns and calculated tables are computed during the database processing and then stored in the model, it will also increase the load time. You can follow this documents to optimize data model and reduse the load time.
The reasons about load time can be also the following:
1. Data Model (rows, columns, tables, you can follow this article to optimize the data model)
2. Hardware Performance (either be data source or computer running power bi desktop, check usage while importing to see if any one reach the bottleneck)
3. Network Performance(mainly when using gateway to imported into service, check the gateway bandwidth usage while refreshing)
Best regards,
Community Support Team _ Dong Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
HI Anonymous ,
Based on this document: Data refreshes must complete in less than 2 hours if it is not in premium node.
If you are using the Import mode, th loading time depens on the size of your model (rows and columns), network status between pc and datasource, and also the performance of pc which runs the power bi. At last, calculated columns and calculated tables are computed during the database processing and then stored in the model, it will also increase the load time. You can follow this documents to optimize data model and reduse the load time.
The reasons about load time can be also the following:
1. Data Model (rows, columns, tables, you can follow this article to optimize the data model)
2. Hardware Performance (either be data source or computer running power bi desktop, check usage while importing to see if any one reach the bottleneck)
3. Network Performance(mainly when using gateway to imported into service, check the gateway bandwidth usage while refreshing)
Best regards,
Community Support Team _ Dong Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi v-lid-msft ,
Thanks for your reply.
I'm not sure if your solution applies to me, considering I don't use the "Import Mode"; or at least I think I don't?
As I mentioned in the OP, my dataset is housed on a Panoply Cloud-based Data Warehouse. I'm assuming Power BI service is connecting to it directly? Additionally, I'm aware that the timeout is limited to 2 hours, however, I'm finding it hard to believe a direct data warehouse connection will take longer than 2 hours to update data, unless it's truncating everything and reuploading it all brand new.
Hoping for some more ideas here... I'll also reach out to Panoply Support to see if they have any insights as well.
Thank you,
Curtis
Hi Anonymous ,
Based on this document, panoply supports the Direct Query Mode that Power BI will query your Panoply data warehouse directly when you report page. But we notice that you mention manual and scheduled refresh is up to 2 hours, so we assume that you choose the Data Connectivity mode as Import when you first connect to the Panoply, Cloud you please check it in your PIBX file?
Best regards,
Community Support Team _ Dong Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.Ahh you are correct! I will try to move this to direct query and perform other optimizations to see if this solves my problem.