Training Status Unproductive!

All seems reasonable to me. My Training Status was Productive just over a week ago, then went to Unproductive earlier this week after a slower run than normal and a Wattbike session, that between them ever so slightly lowered my VO2 Max by 1 point for both running and cycling respectively and also my cycling FTP went down by 4 watts. After strength training Wednesday and Thursday off, I've gone for a reasonable 10km run today (Friday), with Aerobic TE 3.6 and Anaerobic 2.1, and my running VO2 Max is back to where it was a week ago and my Training Status has moved to Maintaining. I guess I'll see Productive again once I do something to raise my LTHR or FTP ever so slightly (interval training or some such).

I Looked at the firstbeat website for this metric. It appears to be directly related to V02 Max, a small shift down will change it from productive to unproductive. I guess for the cyclist's amongst us a drop in FTP could do the same?
Looks like I need to do some intervals this wknd :)

Same problem here. Aerob 3.5 training https://connect.garmin.com/modern/activity/1714525818 doesn't change from noproductive to productive

Thanks for posting that. I think we're all trying to figure out (1) how this Training Status feature works, and (2) if it works well, if we should pay attention to it. Every time someone shares their experience it helps. A lot of people are saying it works pretty good and we should trust it.

Question: after you did that activity, when it still says unproductive, are you checking on the watch, or on the web?

I'm not sure if I need to get a better HR Max estimate or what.

Better if you can find your LTHR and set your zones from that.

Oops, mispost.

My training status was "productieve" for a long stretch training for the marathon, as well as sometimes "maintaining" or "unproductive", then showed "peaking" and "recovery" during the taper, then after the marathon "productive" again (no runs but due to the marathon itself), now after a first short run unproductive as the VO2 max starts to drop. Pretty good I think. The graph on the iPhone is pretty good.
Freek

Put your chest strap on, edit the "app" settings for your favorite type of exercise (bike, run, etc), add a new data page with two fields: aerobic training effect, and anaerobic training effect. Exercise until you get an aerobic TE of 3.0 or higher. When you stop, (I predict) the watch will have you in a productive status.

See https://forums.garmin.com/showthread.php?374713-Training-Status-Unproductive-decreasing-fitness-increasing-load



This part seems to work pretty well for me.

This is not working för me.

Training Status is related to Performance condition we can have a real Training Status just for running on the flat road anything else will give us a wrong TS. In order to have a real Training status we have to record an activity with Performance conditions data, VO2max, HR ,and Pacce ,a workout with steep climbs it will result a slow pacce and bad performance condition.status will be unproductive.

I think I commented on this in another discussion. The problem is, that performance condition should be measured in relation to the physical conditions during which the run or other activity takes place. Anything that impacts on speed, pace, heartrate etc needs to be part of the equation. A run with a lot of hills will produce a completely different outcome than a run on a completely flat course. Similarly a run at 15 C and below, will produce a different result from a run at above 25 C (as I experienced yesterday) .

Performance condition measurement that is not able to take this into account is only half value at best. The Fenix can measure altitude (never mind technical issues discussed elsewhere), and does indicate "floors" climbed. It also measures temperature (even if that's not the right outside temp when no extra sensor is used - it still give a good impression of the conditions and can serve as a very good indicator as to how performance is impacted). It is also conceivable to link to weather web services and link to actual climatic conditions, and to link the altitude measurements to the GPS track etc etc. This could be factored into the calculation. So I don't accept that "anything but a flat road will give us wrong TS". It just needs to be built into the model.

this is so discouraging.   i am actually getting rid of the Fenix6 

`i am 67 years old and went from doing absolutely nothing in 10 weeks to run 5 km every other day.   and my watch encourages me by telling me my training is unproductive.