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

Compete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.

Reply

Schedule runs in advance (before specified time)

Hi.

I have scheduled a report as follows:

mohammadjavaher_0-1721448512527.png

I have added a card in report which displays date and time of last report refresh, Today I was looking at the report and found out that it has had refreshed today, before 8:15AM

mohammadjavaher_1-1721448594791.png

As report is set to refresh every 3 hours, it's apparent that report is refreshed out of specified hours. I tried to investigate more and found related SQL Server Agent job. I was unable to open job's schedule, as SSMS gives me this error:

mohammadjavaher_2-1721448702931.png

So, I scripted job to see what's inside. Thi is the schedule part:

mohammadjavaher_4-1721448817397.png

This confirms that job should not run before 8:15AM. But there are more strange things here. active_start_time and active_end_time parameters have abnormal values compared to each other. End time comes before start time! Furthermore, why does SSMS give error on freq_subday_interval value? It is set to 180 and doesn't seem strange. Can someone help me on this behavior please?

 

Regards,

Mohamamd

1 REPLY 1
hackcrr
Super User
Super User

hi, @mohammadjavaher 

The discrepancy between the scheduled and actual run times can be caused by SQL Server Agent misconfiguration or time zone issues.
Verify time zone:
You should ensure that the time zone is configured correctly on the Power BI Report Server and SQL Server.
Check if there are discrepancies in the time zone settings.
Since the error occurred in SSMS, try to modify the job schedule using T-SQL.
Correct the active_start_time and active_end_time values. These values ​​should be in the format of HHMMSS, for example, 081500 8:15 AM and 231500 11:15 PM.
Correct freq_subday_interval:
Ensure that the freq_subday_interval value is appropriate for the freq_subday_type. For an interval of 180 minutes (3 hours), the freq_subday_type should be set correctly.

The discrepancy between the scheduled and actual run times can be caused by SQL Server Agent misconfiguration or time zone issues.
Verify time zone:
You should ensure that the time zone is configured correctly on the Power BI Report Server and SQL Server.
Check if there are discrepancies in the time zone settings.
Since the error occurred in SSMS, try to modify the job schedule using T-SQL.
Correct the active_start_time and active_end_time values. These values ​​should be in the format of HHMMSS, for example, 081500 8:15 AM and 231500 11:15 PM.
Correct freq_subday_interval:
Ensure that the freq_subday_interval value is appropriate for the freq_subday_type. For an interval of 180 minutes (3 hours), the freq_subday_type should be set correctly.

After updating the job schedule, verify that it is running properly by monitoring the next scheduled run time.
You can also review the Power BI Report Server logs to identify any anomalies that may be affecting the report refresh schedule.

 

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

 

Helpful resources

Announcements
August Power BI Update Carousel

Power BI Monthly Update - August 2025

Check out the August 2025 Power BI update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

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