Fixing Missing Intervals.icu or Strava Data
Troubleshoot missing activities, missing metrics, or incomplete sync behavior between MyTrainPal, Intervals.icu, and Strava.
Before you troubleshoot, identify where the missing thing should have appeared first: MyTrainPal, Intervals.icu, or Strava. The fix changes depending on whether the problem is a missing activity, a missing planned workout, or missing fields on an imported activity.
Start by naming the missing thing
The quickest way to lose time is to say 'sync is broken' without naming what is missing. A planned workout not writing to Intervals.icu is a different problem from a Strava ride arriving without full metrics.
It also matters which service created the data first. Every extra hop gives another chance for fields to be dropped, delayed, or hidden.
- If a MyTrainPal plan change never reaches Intervals.icu, look at connection state and auto-sync.
- If a Strava activity exists but looks thinner elsewhere, direct Strava import is often the cleanest path.
- If the missing data is recovery data rather than workouts, use the Apple Health or Health Connect guide instead.
Fast troubleshooting flow
Name the missing item exactly
Is it a planned workout, a completed activity, or just a missing field like power, HRV, or pace? That first distinction usually tells you which connection to inspect.
Check the connection status and most recent sync
If the token or account link was revoked, syncing can fail quietly until the connection is refreshed.
Check auto-sync only for write-back problems
Auto-sync matters when you expect MyTrainPal changes to appear in Intervals.icu. It does not explain every missing import problem.
Reconnect the original source directly when needed
If the missing data is Strava-specific, connect Strava directly instead of relying on a re-export chain through another service.
Compare one concrete example before contacting support
Pick one activity or one date and compare it across apps. Support is much faster when you can say exactly what is missing and where it should have appeared.
Problem-by-problem fixes
Planned workouts are not appearing in Intervals.icu.
Check auto-sync first. If the connection is healthy but write-back is off, MyTrainPal can still plan workouts without pushing them to Intervals.icu.
Past activities show up, but some detailed metrics are missing.
That often means the upstream provider is not exposing the same detail through the API path you are using. Connect the source directly when possible.
Data imported through Intervals.icu looks different from data imported directly from Strava.
That can happen because providers have different export and licensing rules. If Strava is the real source you care about, use the direct Strava connection for the best chance of preserving that dataset.
Frequently asked questions
Common questions about setup and how the feature works.
Why does connecting Strava directly sometimes help?
Because it reduces the number of hops between the original activity source and MyTrainPal, which lowers the chance that specific fields are lost or withheld in re-export.
Does a connected status guarantee complete data?
No. A connection can be valid while still returning partial or source-limited data, especially when another service is acting as the middle layer.
Should I reconnect or create a new account connection first?
Reconnect the existing source first. If that does not fix the issue, review whether the right platform is connected directly for the data you actually need.
Why my planned activity was not exported to Intervals.icu
In the event you see some activity is not exported automatically even if auto-sync is enabled. You can always open the activity and select "Export to Intervals.icu" to trigger manual sync.
References & Reading
Internal and external resources mentioned in this guide.