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

Garmin Pace Zones doesn't respect what is defined on TrainingPeaks

Hi,

Not sure if anyone can help me, but I have a coach that use TrainingPeaks to plan my structured workouts and the pace zones defined there, doesn't match when I go to my watch and try to do the planned workout.

Example:

A running workout with 5:47 min/km pace (zone1) when it goes to my Garmin watch, appears that I can run in the interval 5:30 to 6:05 min/km. But 5:30 min/km in TrainingPeaks it's already my zone 2.

Is there anything that I can do to match these training pace zones?

Thanks,

  • I've been seeing this as well with my Training Peaks workouts.  It's not respecting the Pace Zones defined in my Training Peaks workout.  Really annoying.

  • have you try to set on TP a pace with interval and not a fix pace?

  • Yesterday I experienced a bit strange behaviour. My coach has prepared a workout for me. The same happened as it is discussed in this thread. But when I updated the workout a bit it became ok on my watch. I added pace to the title of every item in the workout in the following format: Hard - 4:02. I accidentally put an underscore in one case and after I fixed it the paces became ok on my watch. After this I have absolutely no idea whether it's a Garmin or TP problem.

    (There are % of Threshold Paces in the workout.)

    So I can suggest to try to update the workout and hope that I will be ok when it gets synced to your device.

  • TP help center replied to me with this:

    "Thank you for reaching out. When a workout is sent over to Garmin Connect with a target pace, the workout will always have a buffer range of approximately +/- 5% for pace.  It will never be a single number.  This is by design to prevent getting constant beeping alerts about being outside of the target pace.

    This is why you are seeing the range of 5:30 -6:05 min/km. 77% of your threshold pace is the very upper limit of your Zone 1, so with this buffer range, the range will fall into Zone 2. 

    I hope this helps clarify the pace range. Let me know if I can be of further assistance. "

  • I've been having this same issue with my fenix 5 randomly for about 15 months, now it's constant. My target pace zones in my TP workouts are never shown on my watch, e.g. my warm-up pace in TP will be 5:45/km-5:00/km but when I load it onto my watch it shows me a target zone of 8:20/km-5:45/km.

    If i am doing intervals this becomes even worse as I'll have a target of say 4:10-4:15/km set in the TP workout but my watch is showing a target nowhere near like 5:20-5:00/km. I've basically given up on the TP-Garmin workout auto-sync to my watch now, completely useless.

  • Hello all! If you are experiencing this, please tag me provide the following information:

    1. Screenshot of what your workout shows for pace (or target) zones in TrainingPeaks
    2. Screenshot of what your workout shows for pace (or target) zones in Garmin Connect
    3. A few photos of your watch showing the pace (or target) zones at a few different points during your workout
    4. Let me know if we have your permission to access/view your Garmin Connect account to investigate this issue further and if I may contact you via email
  • Not sure if this was resolved, but I see similar problem.  When I prescribe a specific pace in TP, it transfers across with a range of +/- 5% as described above, which I think makes sense.  However if I try and transfer a pace zone in this example I plan 05:20 - 05:42, then when it appears on my watch (Forerunner 920XT) it is saying 4:26 - 4:44.  I realise that I can solve this by switching to specific pace then the the +/- 5% is broadly in range I am aiming for, but thought I would share this for possible further investigation.  I can supply screenshots if needed.

  • if you can post the requested data in my above comment, I'd be happy to look into this further for you!

  • Happy for you to contact me and/or view my account.

  • This specific issue now appears to be resolved.