We're aware of the various complexities daylight saving time can bring, especially when it comes to scheduling and time-based operations. Here's a brief explanation to ensure clarity when using our services:
1. Using the API:
When you schedule through our API:
Time Format: All times should be given in UTC format.
Daylight Saving Responsibility: It's up to you to ensure the correct timing. If you schedule something for the future and daylight saving time changes in between, you must account for that shift. For instance, if you set a task for 14:00 UTC, and daylight saving changes where you are, the actual local time might be different.
2. Using Our User Interface:
For those using our UI for scheduling:
Displayed Time: The time shown is always in local time. This takes into account the current setting of daylight saving for your time zone.
Example: Let's say you're in Finland, which observes daylight saving. If you scheduled a call during the summer (when daylight saving is on) for 15:00, and the actual date of the call falls into winter (when daylight saving is off), the call would be made at 14:00 local time.
In summary, always be vigilant and aware of the time zone and daylight saving differences when scheduling. While our UI does its best to reflect local time accurately, the responsibility for accurate timing using the API lies with the user.
Should you have any more questions or need clarification, please don't hesitate to reach out to our support team.