2575011 - Scheduled Report execution time changes by one hour after Daylight Saving time transition

A scheduled report runs one hour earlier or later than expected after a Daylight Saving Time change.

SuccessFactors HCM Suite

A report is scheduled to run at a fixed local time. After a Daylight Saving Time change, the report starts running one hour earlier or later than expected from the customer perspective.

The issue is with time zones which do not switch to Daylight Savings at all (such as Singapore) or the time zones that switch on a different days (such as Australia). When the time change the report run one hour difference later from Winter to Summer or vice versa.

Currently, it is not possible to maintain report scheduling dynamically at the exact same local time before and after Daylight Saving Time changes in all time zone scenarios. This is expected system behavior due to time zone conversion and Daylight Saving Time differences.

Workaround
As a workaround, schedule the report twice per day with a one-hour difference between the two runs. This helps ensure that when a Daylight Saving Time shift occurs in one time zone but not in the other, one of the scheduled executions will still run at the expected local time from the customer perspective.

Daylight, Savings, Time, Change from winter to Summer, Report schedule in different timezone, Report Scheduled in Winter time or summer time, Report, schedule, in different timezone, Report Scheduled, in Winter time or summer time , KBA , LOD-SF-ANA-RDT , Report Distributor (Advanced Reporting, ORD) , Problem