Incorporate daylight savings in Cloudworks time zones

Now if I select London time zone in Cloudworks schedule, it will not automatically change the time in accordance with daylight savings in UK, forcing us to adjust the schedule manually. The same goes for other countries with daylight savings.

It would be great, if daylight savings were added to Cloudworks schedule time zones. So choosing a specific city time zone would mean that integrations will always run in local time regardless of winter/summer time change.

24
24 votes

New · Last Updated

Comments

  • Hi - thanks for the suggestion. You are correct that currently, CloudWorks integrations are anchored to UTC, with an offset depending on the specific geography in question (as explained in the Community post below). We are examining an enhancement to allow CloudWorks schedules to be set with reference to the Local time in the time zone of your choice, which would respond to daylight saving changes.

  • The capability to have CloudWorks anchored to local Time of Integration User choice would be great. Today when daylight saving times occurs, it is not enough to recreate the schedule by putting the New Local Time, it works for the first run but then the schedule follow the previous UTC time of the schedule! To avoid such an issue, it appears that workaround is to define Schedule in (UTC+00:00) Greenwich. But this add complexity and integration users must be always aware what is the actual difference between their local Time and the UTC Time, this could lead to errors. And anyway, it requires to update the Schedule each time everytime when change of time occurs, this is a waste time even if it can be automatize with the API.

Get Started with Idea Exchange


See our Submission Guidelines and Idea Evaluation Criteria, then start posting your own ideas and showing support for others!