Series 3 Watch OS 6 Stand goal not working Properly

I am so relieved to find that I am not the only one with that issue, I thought my weird combination of still using a Series 1 watch and being an a 30min off time zone would make my case too exotic.

Experiencing pretty much the same issues and my observations / work arounds so far are this: It appears that a new stand hour can only be triggered between 30-59 of the hour (best results between 40-55). So, I am setting reminders via alarm and then manually start an activity, like indoor walk or 'other' and do something like walking up and down the stairs for 2 minutes. Voila, stand hour (not always, just started one at 8:55, this did NOT trigger that missing hour) ... Pretty annoying overall.

I am pretty OCD / paranoid about that whole ring game since in over 4 years I have not missed A SINGLE DAY, move goal at 1000 cal, exercise and stand rings ... all done, all months 'perfect' ... I am about to hit the 1500 in a streak! Don't want to mess this up because of a software bug

But there are some other kinks as well, like my total on move streak. Activity on my phone seems to be lagging behind ... see below screen from today, Nov 13 ...

And the new longest move streak does not show in the top row of 'recent achievements' ...

Something is really wrong and I fear since it only affects a small user group in 'weird' time zones, it is not on fast track over at apple ... I left my complaints at https://www.apple.com/feedback/watch.html and also forwarded this 'story' to macrumors, hoping they might pick it up ... maybe if someone has ties to some Indian mac websites, get this issue out in the open ...

HI,

I have similar issue with series 5 so far no one from apple seem to have any idea, including the service centre guys. I thought this was an watch issue but looks like a bug in OS. The service centre asked me to give the watch to them but I guess its better to wait for now as many people are facing same issue.

I request everyone to submit this as feedback to Apple so that they could be aware of it.

https://www.apple.com/feedback/watch.html

Regards,

Mohan

I exactly have the same issue. Everything works fine except the stand goal.

1. It doesn't detect my stand goal.
2. In times it does an error stand count. i.e. When I move by 2 pm, it counts as I moved by 3 pm. And it doesn't count anything at 4 pm.

For me it displays the stand hours, but even if I have been active and move around it doesn’t count towards the stand hour. In fact it shows blank space similar to how it is when the watch isn’t worn.

Apple Watch Series 4, 6.0.1 with the same issue. I also live in South Australia with a :30 timezone. Additionally, I was in another state with a :00 timezone (after DST change) and I may have noticed the issue over there as well — anecdotal, I could be mistaken.

This ruined my perfect month goal since DST change. It's not recording stand hours nor giving any reminders before the hour is gone. I'm just going to live without the badge but… you know… a bit demotivating.

It's also recording stand goals ahead of time and here's the screenshot to prove it. Note the time in the upper left and the selected stand hour in the chart. Is my watch stuck in a time distortion field? Do I need to consult with a physicist to restore relative time synchrony? Or, is this yet another timezone bug? (Absolutely, most definitely the latter)

It's most definitely a timezone issue. In that, the stand metrics don't understand a non-whole timezone hour offset. Which is a bit of a rookie mistake for whoever made it. Also submitted as developer feedback (ref: FB7404392). Hopefully that will get some attention.

I am also facing the same issue from the day i updated the watch OS to 6.0 and i am from India where the timezone has an offset of 30 minutes.

The attached screenshot from health app for the stand data clearly shows that the stand hour for 1pm to 2pm is tracked at 12.06 pm itself which is annoying and causing a loss of many stand hours in a data.

Issue is not fixed in watchOS 6.1 either.

I have also been facing the same issue on Apple Watch series 4 since I upgraded to watchOS 6. Even when I’m wearing the watch and all other activity rings are accurate it doesn’t show stand goal accurately.

I am also facing this problem, even after the update to watchOS 6.0.1. I’m guessing that perhaps this bug is happening to those of us who live in India, whose time zone is offset from those of its neighbors by half an hour. It’s as if the watch only records the stand goal according to the next closest time zone to the East, even though it displays the correct time on the watch face itself.

Is Apple already aware of this bug?

I am experiencing this issue for the first time this morning on my Apple Watch 3 with OS 6. It was working fine through yesterday bit stopped this morning. I’ve tried resets etc.

Mine seems to have stopped working after a brief partial charge (battery said 88% when I undocked from official Apple charger).

Very irritating after more than a year of no issues.

Same here. I have been seeing these problems ever since I upgraded to OS6.0 (now on 6.0.1). I have seen two problems. You need to do a lot of moving around for the stand goal to detect. Second problem is with the half an hour offset. As multiple users reported here, stand goal is updated only after half an hour. Assuming that TZ difference (+5.30) is causing this issue. For the first problem, I reset the watch, paired and calibrated. This didn't help either. I'm using Watch Series 3 with OS 6.0.1.

I am also having this problem on my Watch series 3 after the OS 6 update. I believe it is also due to daylight savings changing in AUS and becuase I live in SA which is +9.5 hours. I think there must be a bug with the .5 hour regions judging from this thread. Similar to what is happening with others my stand goal will record an hour ahead and I will also not get stand goal reminders at 50 minutes past. I hope we have a solution soon.

Some of you who are still in the warranty period may want to raise a support request. We don’t know if Apple is aware of this issue. Though this discussion has been going on for a month, 6.1 didn’t have a fix for this. We need to get it fixed at least by next patch release.