Automations Disrupted by Local Time Change - Daylight Savings

I found that all of the trigger times for my automations were pushed back one hour after daylight savings. This caused some of my automations to stop functioning. I was told by Monday representatives that this is expected with local time changes such as daylight savings time change. I request an update/change in Mondays automations capabilities so that the program can recognize these time changes. Automation rules (including the trigger times) should not change without user interaction.

I was also plagued by the same condition and agree that there should be an automatic DST adjustment available. This otherwise impacts scheduling and creates overhead by having to manually reset each automation.

1 Like

Monday - is there an update happening to accommodate for daylight savings time as noted above? Daylight Savings Time just began, so my automations were pushed back an hour, instead of staying at the time they were set for in the automation recipe.

This is not ideal, please update.

1 Like

I just had the case 2 weeks ago.
Some of my automations, planned a 23:30 were pushed by 1 hour. They were then planned at 00:30, but the same day instead of being pushed to the next day… So they didn’t trigger at all.
I would understand if monday would say they don’t take into account the local time and that all automation trigger universal time. But don’t change the running time I spent hours on optimizing.
This is a major flaw that needs to be fixed asap.
I can’t change all automation running times every 6 months. And it’s not always possible to avoid the 23:00 - 01:00 am window…
Thank you for your action