TrainingPeaks workout not syncing to Polar Flow: the documented causes

Start with the clock, not the workout

TrainingPeaks plans sync to Flow automatically once a day [Polar TrainingPeaks Sync]. That is the single most common reason a workout you scheduled twenty minutes ago is not in your diary. There is a manual Refresh button in the Flow calendar view that triggers the sync immediately, and it is easy to miss.

Once you link the accounts on Flow's Partners page, every compatible TrainingPeaks training plan and all target workouts you make will sync to Polar Flow automatically once a day [Polar TrainingPeaks Sync]. Once a day is the contract. A coach who adds tomorrow's session at 9pm and a rider who checks the watch at 6am the next morning may simply be inside the same sync window, with nothing wrong at either end.

The second clock-shaped cause is a stale link. When Polar extended the integration to carry structured workouts and training plans in the TrainingPeaks-to-Flow direction, existing users had to reconnect their accounts for the new direction to work [Polar TrainingPeaks Update]. Before that change the sync only ran the other way, from Flow to TrainingPeaks. An account linked before the change and never re-linked will keep uploading your completed rides perfectly while never delivering a single planned workout, which is a confusing failure because half of it works.

So the first two things to do are press Refresh in the Flow calendar, and unlink then relink TrainingPeaks on the Partners page. If the workout appears, nothing was broken. If it does not, the cause is one of the content rules below.

The rules that reject a workout outright

One rule accounts for most hard rejections and it is a number: in Flow the number of unique phases allowed in a training target is limited to 20, so a TrainingPeaks target containing more than 20 phases cannot be synced to Flow at all [Polar TrainingPeaks Sync].

Twenty sounds generous until you count the way a workout builder counts. Every warm-up block, every work interval, every recovery interval and every cool-down is a phase. A session written as ten by three minutes with three minutes recovery, plus a warm-up and a cool-down, is twenty-two phases before you add anything else. Sessions with short reps hit the cap fastest, which is why the workouts that vanish tend to be the VO2max and anaerobic ones rather than the endurance rides.

The word unique is doing work in Polar's phrasing, so a repeating block expressed as a repeat rather than as expanded steps will generally survive where the expanded version will not. If a session you need is over the limit, the practical fix is to rebuild it in TrainingPeaks using a repeat structure, or to collapse the warm-up from four graded steps into one.

The other outright rejection is narrower and worth knowing if you cross-train: Polar supports only the Old Strength Builder workout type, not the New Strength Builder [Polar TrainingPeaks Sync]. That does not touch cycling sessions, but a mixed plan can appear to sync partially, with the bike work arriving and the gym work silently absent.

The rules that change a workout on the way through

Two documented transformations catch riders who assume a synced workout is an identical copy. Flow always uses five training zones while TrainingPeaks does not restrict the number, so zones are remapped to be compatible with Flow on sync [Polar TrainingPeaks Sync]. And TrainingPeaks does not separate indoor cycling from outdoor cycling the way Flow does.

Take the zone remap first, because it produces the report that the workout synced but the targets are wrong. If your TrainingPeaks plan is written against a seven-zone or eight-zone model, Flow has to compress it into five on arrival. The session structure survives; the intensity boundaries are Flow's, not TrainingPeaks'. A target written as the top of zone 3 in an eight-zone model does not land at the top of zone 3 in a five-zone one, and no error is raised because nothing failed.

The sport-profile mismatch is the subtler one and Polar gives the fix directly. Because TrainingPeaks has fewer workout types than Flow and does not separate indoor from outdoor cycling, Polar recommends that if you only do indoor cycling in Flow you should also keep the regular cycling sport profile in your favourites, with custom zones turned on [Polar TrainingPeaks Sync]. Without that profile on the watch, the target has nowhere to land and the structured guidance does not appear even though the session is in your diary.

Two smaller transformations round it out. Flow imposes a 45-character limit on the title and a 500-character limit on training notes, so long workout names and detailed coach instructions are truncated. And once a workout is in your Flow diary you cannot edit it in Flow, only in TrainingPeaks [Polar TrainingPeaks Sync] — which means an attempted fix made on the Polar side has no effect and will be overwritten on the next daily sync.

When the sync is fine and the plan is still wrong

Worth separating from the troubleshooting above, because it is the more common complaint underneath it. A workout that arrives exactly as written can still be the wrong workout, and no amount of sync diagnosis will surface that. This is the gap that training with a Polar keeps running into.

The TrainingPeaks-to-Flow pipe is a delivery mechanism. It moves a decision that something upstream already made. If that decision was made ten days ago against a week you then did not have — you missed Tuesday, you rode four hours unplanned on Saturday, you caught a cold on Thursday — the sync will deliver Thursday's threshold session on Thursday with complete fidelity, and it will be wrong.

Polar's side of this is documented and finite. Its public AccessLink API exposes read endpoints for exercises and activity and nothing that creates a training target [Polar AccessLink API], which is exactly why TrainingPeaks' partner integration is the only door and why no other service can push a session to your watch. Polar built the delivery layer and the measurement layer and left the decision layer to whoever you connect.

That decision layer is where AdaptCycling works. We read the rides your Polar records, build the plan from what you have actually been doing, and rewrite it when the week goes sideways instead of re-delivering a stale calendar. We cannot push the result to your watch, for the API reason above, so the honest arrangement is that the plan lives in the app and you rebuild today's session as a phased training target in Flow if you want it on the wrist [Polar Training Targets].

Quick answers

Sources cited in this guide

1. 01
   Polar TrainingPeaks Sync. Using Polar Flow with TrainingPeaks. Polar Support.
2. 02
   Polar TrainingPeaks Update. Polar Flow update - Further integration with TrainingPeaks. Polar Support.
3. 03
   Polar Training Targets. How do I create a training target in Polar Flow web service?. Polar Support.
4. 04
   Polar AccessLink API. Polar AccessLink API. Polar Developers.

More inside Training with a Polar

Other articles in this series

1. 01

   Does Polar have a cycling training plan?

   Polar's own plan menu lists five options and not one is cycling-specific. What each actually does on a bike, and what Polar says about the gap.

   →
2. 02

   Polar FTP without a power meter: what still works

   Polar's Cycling Performance Test needs a power sensor and runs on eight watches. What an HR-only Polar rider can anchor training to instead.

   →
3. 03

   Polar Flow to Strava sync: what it carries and drops

   Flow's automatic Strava sync skips every ride recorded before you linked, drops calories, and needs sample data. What that costs a training app.

   →
4. 04

   Training with just a Polar H10 and no watch

   An H10 and a phone is a complete free training stack for a cyclist. What Polar Beat records, what the strap's memory does, and where it stops.

   →
5. 05

   Is Polar FitSpark any good for cyclists?

   FitSpark cardio sessions run in any sport profile, so they do work on the bike. Why a daily suggestion is still not a cycling training plan.

   →