App reduced Cardio Load

[YachatsMike]

App did a weird thing.  I recorded a 40 minute Spin this morning for a cardio Load of 66, pretty much what I expected given my heart rate and duration.  This afternoon, the Cardio Load attributed to the Spin had dropped to 1 and the original score added to General Activity.  The Cardio Load graph still shows the gain in the exercise block.  The Zone Minutes and Calories were unaffected.

I reloaded the App but nothing changed.  It's not that big a deal but it still bugs me.  I plan on spinning again tomorrow so we'll see if it does it again.

[alexthecat]

@YachatsMike I have seen that error, but it has never been a consistent thing. It just seems to happen once in a while for no apparent reason. I'm looking forward to hearing whether you see this again tomorrow. 

[YachatsMike]

The ghosts have departed.  Working okay today.

[YachatsMike]

Did it again.  40 minute treadmill walk, 70 Zone Minutes. 435 calories, Zero Cardio Load.

Cardio Load tab shows about 70 points earned during exercise time but credited it to General Activity..

Good thing I know how to figure my own TRIMP..

.

[alexthecat]

@YachatsMike which app version do you have? 4.60 is rolling out now and that should fix this for you going forward. I don't think it will be retroactive though. 

[YachatsMike]

Just updated to 4.60.  We'll see how it goes.  I'm due for another tread day tomorrow.

[YachatsMike]

Alexthecat, I calculate my own TRIMP score so I'm good. Mine may not be as accurate, though because I base mine on my average heart rate for the whole exercise.  Fitbit figures it many times during the work out.  TRIMP as calculated by the App uses an exponential formula so the more often it samples, the more accurate it is.

[YachatsMike]

First exercise since I loaded 4.60.  Cardio Load worked correctly.  But I've been here before.  I'll give it a couple weeks before I call it fixed.

[YachatsMike · Accepted solution]

Hey, I just noticed.  4.60 not only fixed my last exercise but it fixed all my bad ones from before, too. They must have found the code glitch and fixed it