You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Daylight Savings Time Create Recurring Window #584
It seems like the bug fixed here, Azure/azure-sdk-for-java#48363, should also exist in .Net. The issue seems to be that creating a recurring time window filter over the day that is day light savings time results in an error in our validation.
When we implement recurring timewindow filter, we discussed the problem of daylight saving time and we also checked how outlook handled it. My memory tells me that outlook has a very long region list. Different regions has different timezone and different start&end of daylight saving time. So the conclusion is that the cost to support daylight saving time is too big.
And another reason is that at that time we expect that feature flag runs on the server, server can be deployed anywhere, so for server, time should always use UTC time. for certainty.
Activity
zhiyuanliang-ms commentedon Mar 19, 2026
When we implement recurring timewindow filter, we discussed the problem of daylight saving time and we also checked how outlook handled it. My memory tells me that outlook has a very long region list. Different regions has different timezone and different start&end of daylight saving time. So the conclusion is that the cost to support daylight saving time is too big.
And another reason is that at that time we expect that feature flag runs on the server, server can be deployed anywhere, so for server, time should always use UTC time. for certainty.
zhiyuanliang-ms commentedon Mar 19, 2026
Another low cost solution could be adding an option for the timewindow filer to indicate whether to use local time.