I have already contacted Garmin support via email, I am only posting this here for visibility.
I live in a city (Toronto) that observes Eastern Time with daylight saving time, meaning that on Nov 2, 2 AM local time (Eastern Daylight Time / UTC-4), clocks were moved back 1 hour to 1 AM Eastern Standard Time (UTC-5).
The day before that (Nov 1), my watch recorded 26k-ish steps, of which 7.5k-ish were recorded in the final hour (11 PM to 11:59 PM).
After syncing with Connect:
- my watch still shows 26k-ish steps for that day (and a green bar indicating I hit my auto goal of roughly 26k steps). It also shows that my daily steps streak was extended
- Connect shows only 18k-ish steps, and a blue bar indicating I did not hit my goal. Ofc, my current goal streak has been reset. Also, my auto steps goal has been lowered to 12k ish
Just wanted to post this in case any user or Garmin employee finds it interesting.
Yes, I know that dates, times and time zones are "hard" [*]. I will point out that the watch itself handled the DST transition just fine. (Although I guess the complete test would've been to take steps between 1 AM and 2 AM EDT Nov 2, and see if those steps were erased on the watch by the DST transition.)
[*] I mean unironically they are, although in a perfect world they shouldn't be. One big problem - not limited to dates/times - is that edge cases are rarely tested or even considered.
