Skip to main content

I use Fenix 6S to record my outdoor rowing. Sometimes it shows up in training log as a row but most times just as 'workout'.  I can't figure out why it does this as I follow exact same steps each time.

Screenshot example shows 28Jul 17k row in Blue but 29Jul is also a row but showing small grey dot and no distance.  This happens most of the time and there are plenty more examples.  (11, 12 and 13 Jul are all rows). 

This makes the training log useless for me.

 

Hi ​@JackH,

Just to clarify, are the activities themselves recorded (and displaying in your list of activities) as rowing or as generic workouts? In other words - is only the training log incorrect, or also the activities?

Also, it might help if you add links to two sample activities - one that's ok and one that's problematic - so we can compare. 

Thanks!


Both activities were recorded and show as Rowing.   It’s just the training log that is incorrectly showing as ‘Workout’.  
I think I have identified the cause now though….
This bug was introduced around the same time as ‘Quick Edit’ late last year.  If an activity is saved using QE then it displays  incorrectly. In the training log.  QE also changes what information is displayed for the activity which is less useful than the normal summary (QE removes the  ‘Pace’ stats’)..  I use an Android phone.

Examples here from last week, on consecutive days. You can see the summary data is different and the training log incorrect,


https://www.strava.com/activities/15275181426

https://www.strava.com/activities/15195562008
 


Thanks ​@JackH, that's a good catch - personally I don't use quick edit (I don't like it so I always just dismiss it 🙈) so I haven't experienced the issue myself. I've asked the moderators to bring this up with the Strava engineers, hopefully they'll fix the bug soon! 


Hey ​@JackH,

Thank you for providing these examples ​@Jana_S requested.
I’ll relay this to my team to investigate further.

Thank you so much for your patience & cooperation.


Hey ​@JackH,

I can confirm our team is aware of this issue and currently working on a fix.
I’ll return to this thread with an update once I receive more information.


Reply