Ski software · 14 min read

Workout in Apple Health but missing from the app? Trace the data path

Do not check every setting at once. Find the first handoff where the expected data type disappears: in the recorder, in Apple Health, or only in the destination app. A visible workout does not prove that heart rate, energy, distance, or route data came with it.

A skier compares two phones after a test recording; one shows several workout data types, while the other is missing some fields
On this page

Start by naming the problem precisely: “The workout appears in the recorder but not in Apple Health,” or “The workout appears in Apple Health, but the destination app has no heart-rate data.” That tells you which handoff to investigate.

Apple Health does not mirror every screen in a recorder. A workout is a summary and a container. Heart rate, energy, distance, and route can exist as separate data types or associated samples. The recorder decides what to write; the destination app decides what to read.

Seven handoffs, not a vague “sync problem”

Work from left to right. When the category you need first goes missing, stay at that handoff and check only the items listed there.

  1. Recorder

    Did the app or device save the full test recording?

    You can see the start, end, and a saved summary.
  2. Write

    Can the recorder share workouts and the expected categories with Apple Health?

    Writing permission is active for the specific category.
  3. Workout

    Does the workout itself appear in Health or Fitness?

    The activity type, time, and duration match the test recording.
  4. Category

    Are heart rate, energy, distance, or route present in addition to the workout?

    The specific category has a matching entry at the workout time.
  5. Source

    Which app or device wrote this entry?

    The expected source appears under “Data Sources & Access.”
  6. Read

    Can the destination app read this exact data type?

    Read access is active on the destination app’s Apple Health page.
  7. Refresh

    Did the destination app read the data again after permission was granted?

    You opened the app, triggered a refresh, and checked the result and timestamp again.

Before diagnosing, decide what should arrive

Check the recorder’s current help documentation. A field promised only in its own report does not have to reach Apple Health.

Before diagnosing, decide what should arrive

Data type Clarify before the test Passes when
Workout Does the recorder export a completed workout record? Type, start time, and duration match in Health or Fitness.
Duration Does the destination app use workout duration or active time? The expected definition is present, rather than only a recorder display.
Heart rate Did the device measure it, and does the recorder write the samples to Health? Heart-rate samples from the expected source appear at the workout time.
Active energy Does the recorder write active energy or only its own calorie estimate? The category contains matching samples from the expected source.
Distance Which distance type does the app export, and can the destination app read it? A matching distance value appears in Health.
Route Does the app export a HealthKit workout route, or does it keep the map inside the app? A route is attached to the workout and shared with the destination app.

Workout

Clarify before the test
Does the recorder export a completed workout record?
Passes when
Type, start time, and duration match in Health or Fitness.

Duration

Clarify before the test
Does the destination app use workout duration or active time?
Passes when
The expected definition is present, rather than only a recorder display.

Heart rate

Clarify before the test
Did the device measure it, and does the recorder write the samples to Health?
Passes when
Heart-rate samples from the expected source appear at the workout time.

Active energy

Clarify before the test
Does the recorder write active energy or only its own calorie estimate?
Passes when
The category contains matching samples from the expected source.

Distance

Clarify before the test
Which distance type does the app export, and can the destination app read it?
Passes when
A matching distance value appears in Health.

Route

Clarify before the test
Does the app export a HealthKit workout route, or does it keep the map inside the app?
Passes when
A route is attached to the workout and shared with the destination app.

Check one test workout from start to finish

Use the real recorder app, device, and export path that you will use when skiing. This browser keeps the entries on this device and does not send them to SlopeReady.

Fields checked: 0/6 0/6
Status
Workout
Duration
Heart rate
Active energy
Distance
Route
  1. Keep the original

    Leave the test recording in the recorder and note its time, device, and app version.

  2. Find the workout

    Check the type, start time, and duration in Health or Fitness. A similar activity from the same day is not enough.

  3. Open each category

    Check heart rate, active energy, distance, and route separately. A workout card does not replace this check.

  4. Identify the source

    For each important category, open “Data Sources & Access” and note who supplied the entry.

  5. Check read access

    Open the destination app’s Apple Health permissions and check the specific category, not only the general app switch.

  6. Refresh once

    Open the destination app again after granting permission and use its documented refresh. Do not repeat the same steps at random.

  7. Note the first failure

    Write the result as a handoff: “Heart rate is present in Health but does not appear in the destination app after refresh.”

Keep your observation separate from the next check

This table does not name a certain technical cause. It points you to the next place where you can find verifiable information.

Keep your observation separate from the next check

What you observe Next check What you still cannot conclude
The recorder has no saved activity Start, stop, saving, device connection, and the recorder’s current help documentation That Apple Health deleted the recording
The recorder has it, but Health has no workout Write permission for workouts, export switch, manual export, and compatible activity type That the destination app caused the problem
Health has the workout, but no heart rate Heart-rate measurement during the test, write permission, and the heart-rate source at the workout time That your heart rate was zero
Health has the workout and heart rate, but the destination app shows nothing The destination app’s read access, the shared time range, and its documented refresh That the destination app can reliably tell whether you denied access
Only the recorder shows the route Current export documentation and route-writing permission That Apple Health or another app can reconstruct the map
Two similar workouts appear Source, start time, and the current duplicate guidance from the apps involved That Source Priority removes the duplicate automatically
Values from different sources overlap Data Sources & Access and the order for that exact category That the top source fills in missing data types
The workout appears later The time of the recorder’s and destination app’s last refresh, plus background and network conditions A fixed universal sync time

The recorder has no saved activity

Next check
Start, stop, saving, device connection, and the recorder’s current help documentation
What you still cannot conclude
That Apple Health deleted the recording

The recorder has it, but Health has no workout

Next check
Write permission for workouts, export switch, manual export, and compatible activity type
What you still cannot conclude
That the destination app caused the problem

Health has the workout, but no heart rate

Next check
Heart-rate measurement during the test, write permission, and the heart-rate source at the workout time
What you still cannot conclude
That your heart rate was zero

Health has the workout and heart rate, but the destination app shows nothing

Next check
The destination app’s read access, the shared time range, and its documented refresh
What you still cannot conclude
That the destination app can reliably tell whether you denied access

Only the recorder shows the route

Next check
Current export documentation and route-writing permission
What you still cannot conclude
That Apple Health or another app can reconstruct the map

Two similar workouts appear

Next check
Source, start time, and the current duplicate guidance from the apps involved
What you still cannot conclude
That Source Priority removes the duplicate automatically

Values from different sources overlap

Next check
Data Sources & Access and the order for that exact category
What you still cannot conclude
That the top source fills in missing data types

The workout appears later

Next check
The time of the recorder’s and destination app’s last refresh, plus background and network conditions
What you still cannot conclude
A fixed universal sync time

Writing and reading need separate permissions

The recorder needs permission to write the data types it should send to Apple Health. The destination app needs permission to read them. A green switch on one page says nothing about the other direction.

HealthKit also protects your privacy: for an individual data type, an app cannot reliably tell whether you denied read access. An empty query can mean that no matching data exist or that the app cannot read them. Check the permission in Health or in system settings instead of waiting for an unambiguous error in the destination app.

A workout is not its details

The workout record can exist while heart rate, energy, distance, or route data are missing.

Sources differ by category

An app can write a workout while the watch supplies heart rate and another source supplies energy.

Priority does not create data

Source order affects overlapping values. It does not restore a data type that was never written.

Forwarding can narrow the data

An intermediary can pass on less data than it displays. Check every handoff against the provider’s current documentation.

Apple Support: Manage Health data, apps, and sources, Apple Developer: Authorize access to Health data, Apple Developer: The structure of an HKWorkout, Apple Developer: Workout routes as a separate series

Turn “sync is broken” into a useful support request

Share only the details needed to investigate the fault. Routes, health values, and account data can be sensitive, so redact them unless support explicitly needs them.

  • Device, operating system, recorder version, and destination app version
  • Time and activity type of the test workout
  • Expected category and why you expect it
  • Last place where the value appears
  • First place where the value is missing
  • Displayed source and checked read or write permission
  • A manual export or documented refresh you have already completed
  • Whether a similar or duplicate record exists

Move only to the next open step

Where SlopeReady sits in this data path

SlopeReady works after the recording. With your permission, the app reads the Apple Health categories it uses for training and recovery. It can place workouts, available details, and other shared signals in the context of your preparation plan.

SlopeReady does not start or stop workouts, record ski runs, GPS routes, or live heart rate, and it does not write to Apple Health. If a workout or data type is missing from Health, the app does not reconstruct it. You can discuss the available data and plan with the AI Coach; a missing category remains visible.

Checked against the app’s read-only HealthKit data path and product contract on August 12, 2026. Data and privacy, Support and product limits

Are the training data you need available in Apple Health?

With your permission, SlopeReady reads the available training and recovery data in Apple Health and helps you discuss it in the context of your preparation plan. Missing categories remain missing.

Explore SlopeReady as a preparation app

Menu names, permission screens, supported categories, and sync rules can change with iOS, watchOS, and app versions. These steps were checked against current Apple and provider documentation on August 12, 2026. Do not delete the original recording until you have saved a usable copy or the support case.