Daylight Saving Time is just around the corner. Here are some key dates and things to consider around these events.
- Daylight Saving Time (DST) in the US will start on Sunday, March 12, 2017 at 3:00am ET. At that time, US clocks will go forward 1 hour.
- British Summer Time (BST) in the UK will start on Sunday, March 26, 2017 at 1:00am UK time. At that time, UK clocks will go forward 1 hour.
- Daylight Saving Time (DST) in Australia will end on Sunday, April 2, 2017 at 2:00am AU time. At that time, AU clocks will go backward 1 hour.
Most modern OS’s will automatically adjust machine clocks, however some may not. AtomSphere logins and the atom communications rely on SSL, which checks to see if the message time matches the registered IP address’ timezone. Also, atom schedules run based on the machine’s clock. Given that security and time are important to machine computation and internet communications, including platform and atom operations, take into consideration that DST changes could have a possible impact to your operations.
Here are some common behaviors to watch out for over the next month, whereby it is possible an incorrect machine clock/timezone setting could be causing the issue:
- you are having trouble logging into the platform (e.g. blank screen or unusual error) that you did not see prior to the DST change
- you do not see any entries in Process reporting starting after the DST change
- Processes don’t run on schedules as expected or there are missed or duplicated schedules
- molecule or atom cloud nodes experience inconsistent behaviors (especially if the clock for some nodes are correct and others are not)
- atoms show offline in the platform.
Always check your machine's clock setting as well as the clocks on the machine(s) hosting your atoms, molecules or clouds and make sure they are accurate to the timezone in which the machine is located.
The root cause for any of the above could definitely be many other reasons, but keep the DST/BST timezone changes in mind just in case.