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:
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:
Do not upload the huge Garmin ZIP file directly. Use the download hyperlink from Garmin’s email.
Correct workflow:
Import All Garmin Data.Links:
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:
Most cases are authentication format issues.
Check these points:
API_KEY (NOT your actual key string).Basic, not Bearer).0 for own account endpoints; i... ids where required).Links:
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: