Fix the scheduler to be aware of daylight saving
The daily schedule I created for 01:00 during British Summer Time has changed to 00:00 now we are back to GMT. Not what I was expecting...
The feature is now available. If you are experiencing any problems, please post a question to the forums (https://social.msdn.microsoft.com/forums/azure/en-US/home?forum=azureautomation) or open a support incident.
Tim Tharratt commented
Hi, I'm still seeing an issue with this. I can choose the time zone in the schedule, but during powershell runtime this isn't adjusted to day lights saving time. If I run the code below on a workstation the time is accurate, as a Azure runbook it's an hour behind.
$VerbosePreference = "Continue"
$time = Get-Date -UFormat %H%M
Actually I think there may be some confusion - there appear to be about three different Azure scheduling related tools i.e. Azure Scheduler, Azure Webjobs and Azure Automation Runbooks... this improvement appears to be specifically for Azure Automation Runbooks (sigh - would be great to have the other two updated accordingly)
I can't see anything about selecting a timezone in the current version of the scheduler. It would be great when these improvements were completed if a short blogpost on their usage could be linked to.
Aamir Yaseen commented
I'm trying to create a schedule webjob to run daily at 2:30 UK Time. I'm unable to find any option in script or in portal to do this. Can you please advise how can I achieve this? or this is still not supported?
Beth - that link just takes me to the portal. Please can you provide more information around the Automation schedules? Ive set my Automation schedules to "UK - UK Time" and this STILL doesnt appear to account for daylight savings time in the UK.
Dan Latvala commented
I don't see an option for a time zone when trying to create a new scheduler job...
Great News. I will be trying this at the end of the summer - instead of updating 10+ events to go back one hour hopefully it will be the last time I have to set them forever!
We have a fix coming soon, but we have a few changes that we want to make before its released.
If you want to try it out an early version of it, you can use this URL: http://aka.ms/newschedulefeatures.
Loganathan PC commented
Is this fixed now?
Douglas James Boyd commented
It's more that you want the script itself to run in the time zone of your choosing, not just the scheduler, so get-date returns your time, rather than UTC or the time zone the engine runs in. EG the Assert-AutoShutdownSchedule script from the gallery uses times you set in tags, but working out what amendment needs to be made to the script to make it match the automation engine isn't easy to figure out. In our case it is scheduled to run every hour, so setting time zone in the schedule won't help. The code below works in powershell, but not in automation...
if ($DST -eq "True")
$currentTime = (get-date).ToUniversalTime().AddHours(1)
write-output "Summertime when the living is easy - $($currentTime) same as UTC plus 1 hour"
$currentTime = (get-date).ToUniversalTime()
write-output "Dark days of winter - $($currentTime) same as UTC"
How much longer till launch?
PRISMA Computer GmbH commented
Still not respecting daylight saving time. My solution is:
* Duplicate all Schedules with 1 hour different time ending with "-summertime"
* Write a daily runnbook checking whether summertime or not and en-/disabling all schedules (not) ending of "-summertime" and vice versa.
Jakob Gottlieb Svendsen (MVP) commented
I had replies today from customer complaining that it has happened again.
This is still an issue. All my job schedules moved from 8AM to 9AM.
Mike Douglas commented
Just got hit by this. I had to recreate my job schedules. Glad to see it is being worked on!
Georgios Diamantopoulos commented
Better be fixed before the next daylight saving :)
Sam Mall commented
I just changed all my automation schedules at the start of November due to BST ending and everything starting an hour early.. however this morning all my schedules ran an hour late... Does this mean it's been resolved?
Martin Bergeron commented
On november 1st, 2015, all my schedules for my runbooks were changed off one hour. Have to edit all planning for each runbook, create a new plan with the right execution hour and deactivate the changed plan. If i'm keeping all this, in march 2016, i would reactivate the old plan which will got now the right time and deactivate the actual plan which should have one hour late. A better solution will be welcomed!
Vytenis Silgalis commented
This is definitely still a problem, any way to escalate this?
Any news on this?