Bug: Running Tolerance is exactly the same on Monday as last week

This bug is still reproducible every week for the last two months. On Monday (first day of the week), impact load and actual distance equals to what I had last week, even though it should be zero:

Thanks for letting us know this is still happening, Attila . I've just reached out over email so we can continue to look into this. Please be on the lookout for that email soon.

Others experiencing this same thing, please bookmark and follow this threads as we will post any meaningful updates here.

Report sent from the Garmin Connect Android app. Thanks for looking into this.

Thank you for your patience. Our internal team looking into this was not ever able to reproduce this and have had no other reports of it occurring by other users. 

Please make sure that your Connect app is on the most recent version (5.27.3). 

Hello Garmin - SP , this still reproduces every single Monday on my Garmin Connect Web and Android app. Not sure how I am this unique snowflake in the entire Garmin system. 

As I gave you permission to check my Garmin account, I don't really understand why you need to reproduce it yourself, you could very easily check my account and have it "reproduced" there on every Monday morning.

Of course if your team is in the US, it won't be that easy, because you're behind my time zone, but for example this Monday I did not have a run, so you would have had the whole day to check. We can coordinate more Mondays like that, if you need to use my account to reproduce it. It's just weird you did not do that, when it's easy, especially that you asked for permission to do it.

I'm going to keep trying to figure out what causes this, as it seems the developers can't, but to make sure we're on the same settings, can you ensure that in at these two places, you have the same options selected as me? Go to

• https://connect.garmin.com/app/settings/displayPreferences and
• Garmin Connect Android -> More -> Settings -> Users Settings

And ensure you have the following set, which might affect the reproducibility:

• Measurement Units: Metric
• First Day of the Week: Monday

I now switched to Sunday to see if that will affect anything for next week, as I assume you people in the US like to set this to Sunday, which would affect when the calculation for the week triggers.

EDIT: oh, and yes, I'm on 5.27.3, and I keep it always up to date. But as you could see from everything I posted here and sent you in mail, this happens on Garmin Connect Web as well, so it has nothing to do with the app, it's the backend data that has issues.

Our internal teams like to try and reproduce situations like this especially in the event only one reported user is having this experience. Since they were unable to replicate it and determine what could be the cause of it with the diagnostics you provided earlier on, and with no other users reporting this it is not something that can be fixed as there is no finding what the cause is. 

 Garmin - SP  Hey, I'm a senior software engineer who developed enterprise backend software for more than 10 years. I also like to reproduce issues like this. But when I cannot, and I have access to the problematic system, I go there and check. This is not happening on my watch that I would need to ship to you to check what is wrong. In fact the watch is the only place that is not affected, which is because there the calculation likely happens locally.

This is 95% sure an issue in your backend database servers that you have access to, as we can see this happens both on the Android app and Connect Web, and it would make all the sense to look there, while the issue is happening and find out why those fields are not zero.

Likely cause is that you're not putting zeros in some fields at the start of the week, so the frontends (app, web) are filling in the previous data.

Relevant problems can be time zones and start of the week, when adding the zeros for when the new week starts for each user. This is not an easy problem, because it involves time, and time handling in computers is complicated.

The reason others are not complaining about this is because it might rely on settings that are not that common (start of the week Monday, or non-USA timezones) and also because Running Tolerance is not a feature on a lot of watches yet, so fewer people could encounter this bug.

I don't want to sound like I'm teaching junior developers how to debug stuff, but maybe these are things your colleagues haven't thought about. This bug is actively happening every week in your internal systems. It's not an impossible to study phenomenon that you have no way to reproduce.

Garmin - SP said:

this it is not something that can be fixed as there is no finding what the cause is. 

There are tons of ways to find out what the cause is. Your colleagues might not be able to or don't want to do it, because it's low priority. But let's not say it cannot be done.

I switched from

First Day of the Week: Monday

to

First Day of the Week: Sunday

This just discovered another embarrassing set of bugs with a 6 day week and broken chart drawing.

At this point I won't put more effort into explaining it than my annotations, because frankly I got tired of debugging stuff for you for free. It really feels like you're doing me a favor here, not me helping you fix your subpar implementation of a new feature.

However it's clear you have a boatload of bugs around this feature and time (when values are recalculated and when weeks start). See pictures:

Now I'll switch back to First day of the Week: Monday and see what that does.