Power Bi Paginated Report Subscription run 1 hr after daylight saving change

[gha]

Hi, I am currently in Central Time Zone. When I subscribe to a Pagniated report From Power Bi Server a week ago at 12 AM Central.

It schedule to run at 6:00 AM UTC.
After Daylight Saving time, Central Time lost 1 hr, so now the Schedule Report run 1 hr late.

is there a way to change On Premise Power Bi Report serve to Central? or anyway to fix this ?

one of my solution is to create a job to get all the report subscription and adjust it's time.

[v-henryk-mstf]

Hi @gha ,

Whether the advice given by @d_gosbell  has solved your confusion, if the problem has been solved you can mark the reply for the standard answer to help the other members find it more quickly. If not, please point it out.

Looking forward to your feedback.

Best Regards,
Henry

[gha]

Thank you for your information.

my server is currently running in UTC and Adjust for daylight saving time is turn off.
turning this on might fix mine issue then

[d_gosbell]

---

@gha wrote:

Thank you for your information.

my server is currently running in UTC and Adjust for daylight saving time is turn off.
turning this on might fix mine issue then

---

Possibly not. I do not believe that the UTC timezone has daylight savings. If you cannot change the timezone of the server you will probably need to look for other solutions. You will probably need to test if doing some sort of minor change to the schedule (like adding a space to the name) will cause the server to reset the time with the updated offset from UTC. Or you may need to manually adjust all the schedules twice a year to account for daylight savings.

[gha]

ok, i will try those scenerio, Thank you!

[d_gosbell · Accepted solution]

I've been running PBIRS since 2018 and have not seen this issue. It would be worth checking the time zone settings on the SQL Server that is hosting the ReportServer database. PBIRS will create SQL Agent jobs on this server to trigger any scheduled operations so if this server is not set to observe daylight savings it might cause this issue. 

If you can't change the timezone on this server for some reason and you need to adjust all the report subscriptions you should either use the user interface to do this or the REST api. The reason for this is that the schedule information is also written to a table in the ReportServer database and if those two are out of synch you could end up with 2 copies of reports going out (and you should never edit the database tables directly)