Hello,
I am investigating structured running workout generation for Garmin devices (Forerunner 965).
I observed the following behavior:
Route A
RestOrTrain → Garmin Connect → Forerunner 965
Pace targets and HR targets work correctly.
Route B
Intervals.icu → Garmin Connect → Forerunner 965
Workout structure and HR targets are imported correctly, but Pace targets are often lost.
Route C
Intervals Workout Text → Garmin Connect → Forerunner 965
Workout structure is imported, but Pace targets are not recognized.
I also confirmed that:
- Pace-only workouts sometimes succeed.
- Mixed Pace + HR workouts often fail.
- Garmin Connect still imports the workout structure correctly.
Key observation:
**The exact same Pace targets work correctly when generated by RestOrTrain and synced through Garmin Connect, but are often lost when generated through Intervals.icu.**
My question is:
Is this an expected limitation of Garmin Connect's external workout import process, or is there any public documentation regarding running pace target definitions (for example, `speed`, `pace.zone`, or related target types) for structured workouts?
Any guidance would be greatly appreciated.
Thank you.
