Hi @devin.tiemens ,

It would be nice if TimeXtender could have logic that allows you to specify a schedule in any locale and have it automatically correct for DST and map it to UTC which TX uses internally.

Other than that there isn't really a way around this at the moment other than to petition the Council of Europe and national governments to stop wasting time and do away with DST . If you have your VM set to UTC that at least alleviates the discrepancy between ODX Server and TimeXtender scheduling.

Hi,

I totally agree in both cases :)
But I believe the fastest way to solve this is for us to be able to use server time for scheduling.

Hi,

Thanks for the repies I think I should changes this dicussion into an idea then. Especially since I am not in the position to petition the DST at the Council of Europe .

Kind regards,

Devin

Hi guys

It could be an idea to add this to the idea we got here.

I think this idea mainly is about local time, but I agree it could be done for utc in the background but visually it is always in local time.

Hi Thomas,

Thanks, I have upvoted the idea! Hopefully this will be solved in the upcoming updates so that when summertime starts next year we don't have to change all te scheduled times again.

@Thomas Lind,

Can you give an update if this topic will be updated in any update soon with coming summertime in mind? Currently our team is planning to change schedules at our clients before summertime starts, but would be good to know if this will be fixed by an update.