Next week’s runs are already in your head, yet the watch still shows yesterday’s task. With Polar Flow, writing a plan is often easier than tracking where its final version lives: web calendar, phone app, Favourites or your wrist. A clear workflow connects these four places.

Flow is both a phone app and a web service. Using official descriptions checked on 21 November 2026, we cover planning, syncing and partner connections, including newly supported H10 memory recording. This is a documentation-based explanation, rather than our own device test; numerical examples check editing, rather than prescribe individual workouts.

Mobile and web share an account but suit different situations

Polar describes Flow as a free training and activity platform connected to its devices, accessible by phone and browser. The official Polar Flow introduction brings training, activity and recovery data into one system. Mobile and web are not therefore identical in every detail: a quick daily check and editing a complex weekly plan have different clarity needs on different screen sizes.

The phone is convenient for checking a newly saved run and connection status. A computer calendar makes it easier to view work, travel and several workout details together. Choose one place to finalise the weekly plan, then check other views from there. Editing simultaneously in both interfaces makes remembering which version should appear on the watch harder.

A good Sunday check might ask three short questions: what do you want to run, when does it fit and is the next target already on the watch? Add travel time alongside distances in your calendar. A preset longer run becomes usable when reaching the location and finishing also fit the day. A Flow calendar entry is part of organisation, rather than a substitute for real available time.

Phone minimums and setting up an old watch are separate questions

Polar’s current compatibility page specifies iOS 17 or later, or Android 8 or later with Bluetooth 4.0 capability. Huawei requirements also include AppGallery and Huawei Mobile Services. The official Flow compatibility table treats devices separately; general phone Bluetooth capability alone does not establish the complete workflow.

The same page requires computer-based Flow registration for older M400, M460 and V650 devices before mobile pairing. V650 Android syncing separately requires the phone to operate as a BLE peripheral. When moving such an old device to a new phone, read its specific model row first. If pairing fails, checking preparation is more targeted than repeatedly creating accounts or randomly resetting the watch.

Test a successful move with a known entry. Is the old run visible in the correct account, and does a new short activity appear there too? If history and new recording enter different accounts, syncing may partly work while the log splits. Sign-in, watch pairing and data updating are three separate checkpoints. Briefly note them before connecting another service.

A quick target names a task; a phased target also specifies structure

The mobile Flow guide describes creating Quick targets and Phased targets. A quick target specifies duration or distance, for example, while a phased target arranges successive parts. The Polar mobile target-creation instructions explicitly require watch syncing at the end. A target saved on the phone is a planned object; the watch can use it only after appropriate transfer.

A simple time target may suit a session centred on a defined time frame. A phased structure helps when you want to follow a sequence of parts. Choosing between them does not judge the workout’s value. A clear, well-named time target often makes more sense than an unnecessarily elaborate construction. Add details with real meaning during the session.

Names can also help checking. Instead of ‘Thursday’, a short structure-related name helps identify whether the right task transferred. A name does not replace inspecting internal settings, however: after changing distance or repetition count, reread the entire target. A wrong name irritates; a wrong internal structure changes the whole task’s timing.

A runner and coach review a training log together on a laptop facing them in a clubroom.Enlarge image
Editorial illustration created using an AI tool; not a documentary photograph.

Repetition and transitions give phases their real logic

The web Flow editor offers time or distance phases, repeated blocks and automatic or manual phase transitions. Support for intensity settings also depends on the device; power targets, for example, do not work on every Flow-compatible watch. The official web training-target guide suggests reviewing structure first, then target metric and transitions.

As an editing example, take eight minutes of introduction, four repetitions of a two-minute task and one-and-a-half easier minutes, then six minutes to finish. If both middle parts repeat four times, total time is 8 + 4 × 3.5 + 6 = 28 minutes. Without the last easier section, the structure lasts 26.5 minutes. The one-and-a-half-minute difference is not an app error, but a different repetition setting. Use the example to check the editor’s logic.

Manual transitions provide freedom when a section must fit the location or your decision, but require knowing which control advances it. Automatic transitions may simplify timing, but do not know about a busy crossing. Consider which suits the specific route. In the first trial, inspect steps while stationary, then check alerts and controls on a simple loop.

Keep the Favourites template separate from its calendar copy

Polar’s web description says a favourite target can be used as a template for a date; editing its calendar copy does not rewrite the original Favourite. The separate Favourites management guide also distinguishes device-selected content and its syncing. Removing a target from the watch differs from deleting a service-stored template. This helps organise the log without rebuilding every proven task.

A useful arrangement is a general template and a calendar version adapted to the session. Keep the template name recognisably stable, while checking actual repetitions and time for the day. If an edit is missing on the watch, first see whether you opened the calendar copy or template. Confusing the two objects can look like syncing failed to retain changes.

Turn the route between account, phone and watch into a short check: saved web version, updated mobile calendar, then manual sync and opening on the watch. With several Polar devices, check the active destination too. A favourite assigned to another watch can make the app appear correct while the device worn for running lacks the workout.

A partner plan does not automatically become your own Flow target

Polar’s current TrainingPeaks integration description covers supported plans arriving in Flow and completed workouts returning. An older outbound-only connection needs reauthorisation for plan import. Targets arriving from TrainingPeaks must be edited at the source, rather than in Flow; the document also sets a twenty-unique-phase limit for syncable targets. This is Polar’s official TrainingPeaks guide, rather than a general promise to import every external workout file.

Agree with your coach who owns the plan. If it is created in TrainingPeaks, corrections should originate there; then check the arriving version in Flow and on the watch. A second manually rewritten target for the same day may differ from the original. Discuss the specific date, name and structure so both of you mean the same version. The partner platform’s own service and subscription conditions remain separate.

For Komoot, Polar support currently requires active Komoot Premium to transfer routes to the watch. For Grit X2, Grit X2 Pro, Street X, Vantage M3 and Vantage V3 route transfer, it specifies Flow App rather than computer-based FlowSync. The current Komoot and Flow conditions illustrate why specific content and models matter. Free Flow does not automatically make every partner route service free.

Flow now handles H10 memory too

Polar Flow 7.38.0 release notes for both iOS and Android on 9 November 2026 added support for H10 internal-memory workout recording. The old claim that ‘only Polar Beat can do this’ is therefore no longer correct. The iOS update and Android update specifically concern H10; this must not be generalised into H9 memory capability.

The current recording guide distinguishes H10 use with and without GPS. Phone GPS can provide route, distance and speed while the phone remains with you. Without the phone, H10 memory records heart rate for later transfer to Flow. The current Flow recording instructions therefore distinguish strap-stored heart rate from phone-measured location as separate sources. A strap’s internal memory is not itself a GPS track.

If you want to exercise with only the strap, check starting and later transfer during a short familiar session first. A phone-free heart-rate trace is useful when you know why you selected that mode beforehand. Analysing a trail route needs another source too. Choosing recording mode deliberately matters more than later seeking a missing map in a file that never had location input.

A runner reviews the running week with a phone log and paper notes placed side by side.Enlarge image
Editorial illustration created using an AI tool, showing a review of weekly distance and time spent running; not a documentary photograph.

Free Flow and Fitness Program are separate decisions

Polar Fitness Program’s support FAQ explicitly maintains Flow’s free status while treating Fitness Program as a monthly subscription. Hungary appears in the current country list; the programme requires a Polar watch and appropriate in-app purchasing channel. The official Fitness Program conditions therefore differ from basic log access. Keep personally created targets, Running Program and subscription Fitness Program names separate.

Ask which planning tasks you want to delegate to the system. Your own weekly arrangement and a few clear targets may suffice. Others may find an adaptive programme interesting. Every option still needs space in your real calendar, and no view knows your actual responses completely. Read your own regional purchase offer when considering a subscription; renewal, supported device and programme content matter together.

For sync errors, locate the break in the chain, then export deliberately

Polar’s Android background-operation support says power saving may restrict automatic syncing, reconnection or phone GPS data. Separate settings guidance exists for Huawei and Honor. The Polar background-connection help suggests checking restrictions on the specific app. Screenshots for an older system need not be forced literally onto every menu on a new phone.

Prepare a brief status for support: the saved run exists on the watch, is or is not visible on the phone, and which version appears on the web? Then investigate the relevant link. When Flow and Beat run simultaneously, Polar asks you to close the unused app. Check a newly arrived workout by its specific date, rather than inferring transfer merely from a changed weekly total.

For web export, Polar lists GPX, TCX, CSV and FIT according to purpose. Routes and detailed training data may require different exports; the official Flow export description treats them separately. After downloading, also test whether the destination app imports the file meaningfully. The manufacturer-platform overview gives a broader framework for connections, and the comparison of twenty running apps for choosing. Well-used Flow ultimately forms a traceable cycle: plan, transfer, run and checked log.

Sources

Helpful? Pass it on.