Connect website shows sleep start/end time of -477100:00

After not syncing my watch for a day or so, the Connect website says my sleep started and ended at “-477100:00”

The iOS app doesn’t have the same problem.

To be clear I don’t really care but I think it’s hilariously embarrassing for Garmin. Unless of course they don’t care what users of the website think.

  • My times display all right, and AFAIK nobody else reported it either, so it does not seem to be a general issue. Check whether the time, date, and time zone are identical on the watch and on the computer. Also check the setting "Upload Time Zone" in GC Web at https://connect.garmin.com/modern/settings/displayPreferences 

  • There was post in one of the other threads I am not sure if it was the iOS or android Connect app thread where someone had the same issue. It is not one off issue. 

  • My times display all right, and AFAIK nobody else reported it either, so it does not seem to be a general issue. Check whether the time, date, and time zone are identical on the watch and on the computer. Also check the setting "Upload Time Zone" in GC Web at https://connect.garmin.com/modern/settings/displayPreferences 

    Lmao did you miss the part where I said I didn’t care? I’m not interested in troubleshooting the problem, it’s obviously a bug on Garmin’s end when the watch hasn’t been synced recently and/or sleep wasn’t detected the previous night. Once I synced my watch, it went away. The reason I posted this was just to illustrate why Garmin has a certain reputation for software quality, and to highlight that Garmin obviously doesn’t test the website as much as the app.

    Do you really think that displaying times of “-477100:00” is something that can be caused by user error, incorrect time zone configuration or time/date discrepancy? No, it’s clearly an embarrassing coding error on Garmin’s part.

    This is the kind of predictable kneejerk forum response that occurs whenever anyone reports a bug or complains about something that others haven’t seen. “Here’s a generic laundry list of solutions to try” and “it’s probably an issue on your end.”

  • This is the kind of predictable kneejerk forum response

    I'd tell you are overreacting to someone trying to help

  • Thank you for trying to help, but I was publicly demonstrating a bug, not asking for help. Your initial response implied that it's not a bug, but rather a misconfiguration or discrepancy on my end, despite the fact that "-477100:00" is clearly not a valid time under any circumstances. In this instance, it should be very obvious that it's a bug on Garmin's end, even in the extremely unlikely case that any of those suggestions would be relevant here (which they're not).

    Again, I find it very common in user-to-user product communities for the initial response to any post about bugs/problems to be "I don't have the same problem, you're probably doing something wrong", and it's very frustrating.

  • Telling "I do not have the same problem" in no way discredits your report. It only tells that the issue you are reporting is not a general problem, bur rather an effect appearing is some specific and probably exceptional situations (otherwise the forum would be full of similar complaints), and hence my suggestions to check the settings, because excluding or confirming them as the cause would help yourself, other people with the same problem, and Garmin's developers to track down the bug as well.

    I still find you calling me a "kneejerk", as well as your frequent denigrating of Garmin's developers a bit misplaced, and over the edge.