This below is the attached refresh history of one of my report-
I have pro license and I have read that the refresh is timed out after 2 hours, but here I see that there are different refresh times. Some refresh time are 4 hours, some have failed etc. can you explain different scenerios please?
Thanks
Hi @learner03 ,
It seems to me that the time in the refresh history here is not so precise. Refreshes, like queries, require the model be loaded into memory. If there is insufficient memory, the Power BI service will attempt to evict inactive models, and if this isn't possible (as all models are active), the refresh job is queued. Refreshes are typically CPU-intensive, even more so than queries. For this reason, a limit on the number of concurrent refreshes, calculated as the ceiling of 1.5 x the number of backend v-cores, is imposed. If there are too many concurrent refreshes, the scheduled refresh is queued until a refresh slot is available, resulting in the operation taking longer to complete. On-demand refreshes such as those triggered by a user request or an API call will retry three times. If there still aren't enough resources, the refresh will then fail.（refer: link) The start time of the record-breaking period could be the cloud service creates a query and the encrypted credentials for the on-premises data source. (queued time+refresh time)
Pls Try the following ways to check the refresh time。
1.According to the official document, you can select the History view by clicking on History in the refresh summaries page.
In this view, the data associated with a given refresh is based on up 60 most recent records for each scheduled refresh.
2.Use Rest API:
- Returns the refresh history of the specified dataset from "My Workspace"
- Returns the refresh history of the specified dataset from the specified workspace
3. Collect logs from the on-premises data gateway app
Refer to:
https://hatfullofdata.blog/power-bi-dataflow-refresh-history/
Did I answer your question? Mark my post as a solution!
Best Regards
Lucien
Hi @learner03 ,
It seems to me that the time in the refresh history here is not so precise. Refreshes, like queries, require the model be loaded into memory. If there is insufficient memory, the Power BI service will attempt to evict inactive models, and if this isn't possible (as all models are active), the refresh job is queued. Refreshes are typically CPU-intensive, even more so than queries. For this reason, a limit on the number of concurrent refreshes, calculated as the ceiling of 1.5 x the number of backend v-cores, is imposed. If there are too many concurrent refreshes, the scheduled refresh is queued until a refresh slot is available, resulting in the operation taking longer to complete. On-demand refreshes such as those triggered by a user request or an API call will retry three times. If there still aren't enough resources, the refresh will then fail.（refer: link) The start time of the record-breaking period could be the cloud service creates a query and the encrypted credentials for the on-premises data source. (queued time+refresh time)
Pls Try the following ways to check the refresh time。
1.According to the official document, you can select the History view by clicking on History in the refresh summaries page.
In this view, the data associated with a given refresh is based on up 60 most recent records for each scheduled refresh.
2.Use Rest API:
- Returns the refresh history of the specified dataset from "My Workspace"
- Returns the refresh history of the specified dataset from the specified workspace
3. Collect logs from the on-premises data gateway app
Refer to:
https://hatfullofdata.blog/power-bi-dataflow-refresh-history/
Did I answer your question? Mark my post as a solution!
Best Regards
Lucien
Helpful resources
Power BI Monthly Update - August 2025
Check out the August 2025 Power BI update to learn about new features.
Fabric Community Update - August 2025
Find out what's new and trending in the Fabric community.
