Move and exercise rings not working

Force restart both your iPhone and your Watch

First force restart your iPhone by using the method that corresponds to your version of phone, Force restart iPhone

When you see the Apple logo on your iPhone, restart your Watch by holding in both the crown and side button for about 10 seconds until you see the Apple logo and release.

Have the same problem as well, did the forced restarts to both watch and phone, cycled through all of the options for fitness apps I use, and the system settings for locations services, etc. All no-go! Please fix this!!

Anyone know how to roll back a watch update? Thanks in advance!!!!

This appears to be an issue with every update since Feb 2019. I found that if I put the watch on the charger prior to midnight, the watch rings often track properly the following day. If you wear the watch past midnight, the tracking is short changed by as much as 50%. Don't listen to any engineering BS that your heart rate has to be 130 BPM to track properly. My heart rate is in range of 90-115 when it does track correctly. I have told Apple support that they need to fire some software engineers as all my iMacs, iPads, iPhone and Apple watch have been developing issues with every "upgrade to fix bugs". This has been going on since mid 2018.

Can’t edit my original post but this is what worked for me - when I did the forced restart it didn’t work but after I shut both down and waited (took a shower) I turned both on, and the watch started to update the phone for both Move and Exercise.

So, shut both down, wait a moment (or several) then restart both. Worked for me!

*** FIXED ***

I updated my watch Tuesday morning (Aug 27) to 5.3.1 and noticed only my Stand is recording anything. My Move and Excercise are both set to 0 since the update.

I’m having the same problem. Doing the force restarts didn’t seem to help. :(

The reset did not help

Apple Support where are you?

same issue

move and exercise rings showing zero

stand ring working.

Help!!!!

Same here

Just now getting around to reply but the forced reboots on both at the same time (phone first) seemed to fix the issue for me.

This worked for me also. Thank you!!!