Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Letโs celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
Dataset-refreshing is not working in PowerBI service ( Neither Manual nor Scheduled). Source data ( SQL server) is updating daily, So I need to schedule a daily refresh.
Currently, I'm having to refresh data by opening report in desktop and manually refreshing specific query ( right click on query> refresh data) in desktop, and this updates relevant chart with latest data. In this way, I need to refresh queries equal to # of charts in the report to get each chart updated, not a practical solution to be done on daily basis. ( Even in the desktop case, couldn't find a way to update all the charts in one go, Any suggestions?)
In PowerBI service, I get a timeout error ( SS attached) on refresh.
Some unsuccessful attempts to make it work:
Tried clearing Q&A cache, made queries as efficient as I could, disabled refresh for queries related to static data.
Data Cache management Option shows 3.17/ 4 GB
Q&A cache: 10KB
All queries in import mode (As can't afford increased latency coming due to direct queries)
Please help If you ever came across this issue.
Thanks
Solved! Go to Solution.
Hi mayankvijay. A timeout usually means that it's taking to long to refresh. The best idea is to check the performance of the source. Check the time it takes to run the queries outside PowerBi and try improving that.
As a quick fix you can increase the timeouts. By default it's ten minutes. Open PowerBi Desktop and change it if you want to test that:
You can read more about the params for the conection in the docs. There are two types of time out. One for conection and another for command. You can try expanding both just editing the query and modify the PowerQueryM code.
https://docs.microsoft.com/en-us/powerquery-m/sql-database
I hope that helsp,
Happy to help!
Hi mayankvijay. A timeout usually means that it's taking to long to refresh. The best idea is to check the performance of the source. Check the time it takes to run the queries outside PowerBi and try improving that.
As a quick fix you can increase the timeouts. By default it's ten minutes. Open PowerBi Desktop and change it if you want to test that:
You can read more about the params for the conection in the docs. There are two types of time out. One for conection and another for command. You can try expanding both just editing the query and modify the PowerQueryM code.
https://docs.microsoft.com/en-us/powerquery-m/sql-database
I hope that helsp,
Happy to help!
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
52 | |
32 | |
26 | |
26 | |
25 |
User | Count |
---|---|
62 | |
49 | |
30 | |
24 | |
23 |