Related

Two very specific bugs in 16.28

Daern

Bug 1:

Just once, I've had a bug where the notification haptic buzzer on a mid-run alert (probably a "pace too low" sadly) didn't cancel at the end of the alert, leaving the watch perpetually buzzing on my wrist. I got the feeling that this was a race condition with multiple alerts firing at the same time resulting in the buzzer failing to cancel. I was able to cancel the buzzer by changing pace and forcing a "pace too fast" alert which then cancelled the buzzer, but I presume that firing anything that activated the haptics would have cancelled it.

I've only had this once so far and cannot reproduce on demand, but interested to know if anyone else saw it. 

Bug 2:

Following a custom workout, where the final cooldown was heart rate zone with lap button to end, it was impossible to end the workout. Pressing the lap button just resulted in it counting a new lap instead. I had to complete the run in the cooldown phase with the watch moaning at me about my heart rate throughout.

Workout in question:

  • 0

    Not come across the 2nd but definitely the 1st. Came to the same conclusion as you, it was likely caused by more than one alert being triggered at the same time, and triggering another alert cancelled it. Not happened for a good few months now but I did think how annoying it would be in a race environment (only ever happened during a workout up to press). 

  • 0

    I've also had the 1st issue happen to me, only once though. It did seem to be triggered by the pace to slow (or fast) alert. I just hit the start/stop button to quickly pause and unpause the workout, which immediately fixed it.

  • 0

    The first bug happens to me almost every day, when I'm trying to stay within a certain heart rate bpm, but exceed or go under. It seems to happen specifically when I am returning to the target range. Weirdly, once I return to that target range, I get the beep and vibrate (which sometimes doesn't end), but I also see a screen on my watch that still says "too high" or "too low". Usually (if not always) the HR it shows is right at the edge of the range I specified. So I'm guessing it is a race condition right at the edge of HR or pace zones, with two alerts firing at the same time. But I don't ever recall seeing an alert that says something like "in range". Strange.