When we convert workouts now, we convert based on percent of FTP and percent of HR threshold (it’s a bit confusing).
We are going to change this process. This should both simplify it, and make it more flexible. See below the basic idea. That when we convert to HR workouts we will convert to HR zones but this will use the zones from your destination system, like Garmin for example.
Below is example of setting zones in Garmin Connect
Hi,
is this also going to fix the issue with short efforts (ex.20s) convert to low HR values?
Ngl, in the winter I tend to complete most workouts by running outdoors. Couple times I encountered an issue when converting to HR. Short intervals tend to only slightly differ from neighboring segments and the device (in this case Garmin Fenix watch or Garmin Connect) assigns them all to one HR zone. Resulting in well executed internals timing, but I can’t see which segment is WORK and which is REST. the comment section in the intervals also tends to be empty, so I can’t distinguish by that.
Not complaining. Just reporting field tests 
Yes, there is still a bug with these short intervals and should be fixed later this week or next week.
Sweet. Thank you, Alex 
