Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.

Reply
Jeanxyz
Post Prodigy
Post Prodigy

PPU workspace refresh timeout limit

we recently published a report to a PPU workspace. Usual dataset refresh takes 20 minutes, but there are some problem with source data at Jira side, as a result, the refresh in PPU workspace is prolonged to 5 hours. Is there anyway to reduce the timeout limit to 1 hour? There is no way to check the report while the refresh is taking place. 

1 ACCEPTED SOLUTION

Thanks, but none of them work in my case. 

The real problem is with source data at Jira, the import query is very simple, only 2 steps, imported table only contains 150 rows, so the suggestion above won't help. I have also tried reducing the timeout duration in the import query to 5 minutes, but long refresh issue retains.

source =Json.Document(....,[Timeout=#duration(0,0,5,0)]))

 

So as a temporary solution, I moved this problematic table into a seperate data flow and refreshed that table only once a day at non-peak time.  If the refresh fails, it only impacts the data flow, the other tables in the Power BI data model  still get refresh multiple times a day. 

View solution in original post

2 REPLIES 2
v-xinruzhu-msft
Community Support
Community Support

Hi @Jeanxyz 

The Power BI cannot customize the timeout limitation. you can refer to the following suggestion.

1.If your data is too large, you can consider to use incremental refresh if your data source support it, it can improve the refresh speed, you can refer to the following link.

Incremental refresh for semantic models and real-time data in Power BI - Power BI | Microsoft Learn

2.You can consider refactoring the large semantic model into multiple smaller semantic models.

https://learn.microsoft.com/en-us/power-bi/connect-data/refresh-troubleshooting-refresh-scenarios#sc...

3.You can consider to change the import mode to direct mode,it connected to the data source directly, it can optimize the model.

https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-directquery-about#directquery-use-ca...

 

Best Regards!

Yolo Zhu

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

 

 

Thanks, but none of them work in my case. 

The real problem is with source data at Jira, the import query is very simple, only 2 steps, imported table only contains 150 rows, so the suggestion above won't help. I have also tried reducing the timeout duration in the import query to 5 minutes, but long refresh issue retains.

source =Json.Document(....,[Timeout=#duration(0,0,5,0)]))

 

So as a temporary solution, I moved this problematic table into a seperate data flow and refreshed that table only once a day at non-peak time.  If the refresh fails, it only impacts the data flow, the other tables in the Power BI data model  still get refresh multiple times a day. 

Helpful resources

Announcements
LearnSurvey

Fabric certifications survey

Certification feedback opportunity for the community.

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.