This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

discarded rides will be counted by Training Load

when you discard a short ride e.g. 5min because you deteced there is something wrong, missing sensor or so, this activity will be counted by Training Load, but you see this wrong calculation only with active Physio True Up!

Today i discarded a indoor session, because wrong sensor was connected and started a new activity, after my ride i synced Edge 830 (Training Load 399) and Forerunner 945 (Training Load 391)and i have a difference of 8

Anyway, this seems a problem on more devices, because this happens in the past on my Edge 1030 and Fenix 5 too!

of course, i am in a recovery week, my Training Status goes to unproductive, thats really impossible!

EDIT: changed wrong description: discarded instead of deleted

  • I have with my Fenix 5 plus. 

    Since I had found out that F5+ and Edge 530 has a different method to calculate Training Load and so 7 day TL numbers. I decided to save only rides recorded by Edge 530 and then made a sort of sync between these two devices via Physio True Up. Fine.

    But since it happened that one of my ride logged by Edge 530 got corrupted I decided to start the recording on Fenix 5+ too. At the end of the activity I stopped both devices, but saved only the activity of 530. F5+ was in a pending state.

    . After I have seen that everything was fine with the upload of the activity recorded by 530 I stopped F5+ and discarded it. But it did have an effect on the 7 day TL of F5+, even before any sync related to f5+ happened. Moreover my f5+ neglected the activity logged by Edge 530, so the sync of both 530 F5+ had no effect on the TL of F5+.

    It seems that starting, stopping and discarding an activity does not mean a full erase, it makes some “fingerprint, too. Maybe the reason is that if after stopping you wait more than 2 minutes before discarding, you get a recovery heart rate data, and getting this data means a sort of effect on all the physiological measures logged by your device. Maybe. 

    maybe there is just a simple bug, who knows