Workout in Apple Health but not Strava? Check which app recorded it
A workout can be in Apple Health and still be missing from Strava. Before reconnecting everything, check which app saved it.
Strava’s built-in Health import accepts workouts recorded with Apple’s Workout app in the past 30 days. It excludes workouts that other companies’ apps write to Health. That limit is in Strava’s own instructions, checked on 16 October 2026. Turning on Automatic Uploads does not remove it.
Check the workout’s source first
Open the individual workout record in Health and look at its source. A workout recorded on an Apple Watch can still come from a third-party app; the watch alone does not tell you which import path will work.
| What you find | What to try |
|---|---|
| Apple Workout, within 30 days | In Strava, open Settings → Manage Apps and Devices → Health. Check permissions and try Import beside the activity. |
| A different recording app | Check that app for a direct Strava connection or a per-workout sync action. |
| An older workout | Use a supported file from the recording app, or select older Health workouts in WorkoutPort. |
| No workout record in Health | Check the recording app’s Health export. Steps, calories or a workout shown only inside that app are not enough for WorkoutPort to read a Health workout. |
If the recording app’s direct sync does what you need, use that. It may also have data that it never saved to Health.
Where WorkoutPort helps
WorkoutPort reads workouts available to it in Apple Health and sends them through its own Strava connection. Its Health reader is not limited to Apple’s Workout app. You can choose workouts by source, sport and date, including older records still available in Health.
First, allow Health read access, connect the intended Strava account and find one missing workout in WorkoutPort. Send that one and check its time, sport and any route or sensor data in Strava before widening the selection. If WorkoutPort cannot see the workout, fix that read/export problem first.
Example: send gym sessions, leave walks alone
Suppose a gym app saves your strength sessions to Health, but you only want those sessions on Strava. In WorkoutPort, make a rule for that source and strength workouts, with a start date matching when you want syncing to begin. Leave distance and route requirements unset. Check other enabled rules too: a workout can qualify through any matching rule.
| Health workout | Matches this rule? |
|---|---|
| Gym app · strength · 3 October | Yes, even without a GPS route. |
| Gym app · walk · 3 October | No: different sport. |
| Another app · strength · 3 October | No: different source. |
| Gym app · strength · 28 September | No: before the selected start date. |
Matching a rule makes a workout eligible; it does not prove Strava accepted it. Use one upload path for each workout. If the recording app also sends the same sessions directly, turn off that overlapping path before enabling automatic sync.
What this can and cannot fix
WorkoutPort can fill the gap left by Strava’s source filter, but it can only send the workout data it can read. It cannot recover sets, reps, GPS or sensor samples that the recording app did not make available. A basic gym session can still become a Strava activity without a GPX file.
We checked WorkoutPort’s source selection and upload behavior in code and local tests. This is not a compatibility test of every recording app. Try one representative workout before moving a larger history; our migration checklist explains what to compare.