Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
Hi everyone.
We are using PBIRS Sep 2024 edition. We have a lot of reports in this server that using schedule for data refresh. One of those reports has a schedule for every 2 hours.
When we look at ExecutionLog3 table Inconsistency in refreshing cycle time seen. First cycle started at 16:30 PM and it performed in 8:30 PM as well, but in third cycle it fell behind schedule.
We expected it to run at 10:30 PM but it ran at 10:06 PM. For each data refresh cycle the job related to this issue runs once at the scheduled time. In this case, the job ran after the data refresh.
My question is how can I adjust the data update schedule?
Solved! Go to Solution.
Thank you ChrisMuthmann
Hi, @AbbasRzaei8
I think you can check your refresh log file and take the time of execution of the log as the subject matter. This log file is located at: C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\RSPowerBI_*.log
This will give you an accurate picture of when your model initiated a refresh. The traditional workload of a report server is similar to that of a web application. The ability to load reports using imported data or DirectQuery, as well as the ability to perform scheduled refreshes, relies on an instance of Analysis Services hosted with the report server.
You can find information in the Refresh Question document to help you determine why:
Troubleshoot scheduled refresh in Power BI Report Server - Power BI | Microsoft Learn
Best Regards
Jianpeng Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thank you ChrisMuthmann
Hi, @AbbasRzaei8
I think you can check your refresh log file and take the time of execution of the log as the subject matter. This log file is located at: C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\RSPowerBI_*.log
This will give you an accurate picture of when your model initiated a refresh. The traditional workload of a report server is similar to that of a web application. The ability to load reports using imported data or DirectQuery, as well as the ability to perform scheduled refreshes, relies on an instance of Analysis Services hosted with the report server.
You can find information in the Refresh Question document to help you determine why:
Troubleshoot scheduled refresh in Power BI Report Server - Power BI | Microsoft Learn
Best Regards
Jianpeng Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Maybe there is a second job scheduled?
Have a look at the username and the Status, too.
for this report there is only one schedule and one job related to this schedule. But this inconsistency occurs for all reports that using schedule
Hi, @AbbasRzaei8
I wish you all the best. Previously, we provided a solution to help you resolve the issue of discrete data refreshes. Since we haven't heard back from you yet, I'd like to confirm if you've successfully resolved this issue or if you need further help?
If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you for your patience and look forward to hearing from you.
Best Regards
Jianpeng Li
I cannot reproduce this misbehaviour. You have not posted your T-SQL for the ExecutionLog3. I would use something like that:
Select top 100 *
from ReportServerPBI.dbo.ExecutionLog3
where ItemAction = 'DataRefresh'
and ItemPath like '%yourdashboard%'
order by TimeStart desc;
Yes. This is the query that I used
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Prices go up Feb. 11th.
Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.