FAQ Index
This is the navigation topic for all FAQ categories.
This topic is closed for comments to keep it clear and easy to navigate.
This is the navigation topic for all FAQ categories.
This topic is closed for comments to keep it clear and easy to navigate.
This can happen if Strava and another source both import the same workout but with slightly different files (for example different moving time or distance). Auto-matching may fail, so both entries stay visible.
Recommandation: Only keep downloads of activities from the original source. Disable the Strava download option if your activities always come from another source. You can also filter activity types from Strava if you have an activity type that is only synced from Strava.
Also note: Strava privacy circles can affect reported distance/time and increase mismatch cases.
Links:
Yes, duplicates can occur when two direct sources send the same workout (or after reconnect/reimport). Non-Strava source combinations are not always deduplicated automatically.
What helps:
Links:
As a non supporter, the historical download of data from Strava is limited. Though you can request the full history export from Strava.
Links:
Garmin limits historical fetches and so historical backfill can be incomplete or fail (for example duplicate/overlapping request issues). In that case, Intervals.icu may not receive all older workouts automatically.
What to do:
Import All Garmin Data).Links:
What to do: Open Settings → Connections and use Download old data for the affected connection. If you are not a Supporter and have not used Intervals.icu for a while, the connection may have gone dormant. This is usually expected behavior, not a broken sync.
Representative solved threads:
Do not upload the huge Garmin ZIP file directly. Use the download hyperlink from Garmin’s email.
Correct workflow:
Import All Garmin Data.Links:
Strava’s T&C does force to delete all data that were previously transfered. You can request your Data from Strava and Import the complete Data with the Email Link you get from Strava.
FTP in Intervals.icu is copied to each activity. If you change FTP today, old activities are not automatically rewritten.
Best practice:
Edit > Edit).Links:
Usually this is caused by max HR / HR zone settings that are too low (or historically inconsistent).
Fix:
Links:
Most often power clipping is caused by spike settings: values are detected as unrealistic spikes relative to current thresholds.
Fix:
Links:
What to do: Treat eFTP as a suggestion, not an automatic truth. If the estimate looks wrong, do not accept it. Your previous FTP stays in place until you explicitly accept a new value.
Representative solved threads:
Most cases are authentication format issues.
Check these points:
API_KEY (NOT your actual key string and NOT your athlete ID).Basic, not Bearer).0 for own account endpoints; i... ids where required).Links:
If you develop an application and want to integrate via Oauth, then write David a private message according that post:
Moving Time is not always a fixed value in the file. Different platforms calculate it differently from pauses, velocity, and event data, so values can differ for the same activity.
If you want behavior closer to elapsed/recording time, enable Ignore velocity for that activity.
Links:
This is common for indoor sessions, but can also happen for outdoor activities with poor GPS or velocity data. Intervals.icu can underestimate moving/training time when files contain long low-speed or zero-speed segments.
Fix for a finished activity:
Ignore velocity (Actions/Settings).Fix for future activities:
Links:
What to do: Check Actions → Settings → Use elevation correction on the activity. If your device already has good barometric elevation, turning elevation correction on can make the climbing look wrong because Intervals recalculates from map elevation instead of your device data. Turn it off, then reprocess the activity.
Representative solved threads:
Intervals.icu tries to detect intervals regardless of your laps. If you want to use your laps try Actions → Use Laps so Intervals.icu respects the lap markers from your device. You can enable that option per sports category on the settings page, to use Laps by default.
What to do: Assume the problem starts in the source FIT file, not in Intervals.icu. If the device or upstream service wrote the wrong sport type, Intervals can only classify what it receives.
Representative solved threads:
What to do: Check your FTP , resting HR , HR max / threshold settings , and which load setting you are using for each sport. Many solved threads came down to one of these settings being wrong, stale, or inconsistent between sports. If power is unreliable for that sport, switch the load calculation to HR or Pace and update workouts afterward.
Representative solved threads:
Read the linked article or watch the linked video to „learn the basics“:
First check, if you set your intensity settings on the settings page for that activity type (Pace Zones for Pace Targets, Power Zones, for Power Targets, HR Zones for HR Targets).
Check the Quick Guide for Guidance how to write steps, and if there are any errors: