Browse documentation

Reviewing duplicate activities

Find near-matching activity records, compare the suggested keeper and candidate, and remove only the copy you have verified.

Duplicate detection finds records that look like the same effort so you can decide which copy belongs in your training history.

The current check flags activities whose start times are within five minutes and whose distances are within two percent. It reports a suggested keeper and candidate; it does not merge the pair or delete anything by itself.

Checking the suggested pair

Open Activities or ask your coach to scan a recent window. Compare the date, start time, sport, distance, duration, source and any richer detail before you approve a deletion.

The longer-distance record is suggested as the keeper. That is a sorting rule, not proof that it is the better record. A small GPS over-read, more complete splits or a provider-authored source can all matter more than which distance is slightly larger.

Possible duplicate does not mean confirmed duplicate

Two short runs started together can legitimately look alike. Keep both when they represent separate efforts, and delete only after you can identify the extra copy.

Understanding what the scan misses

The comparison needs distance, so a duration-only strength, mobility or climbing activity does not enter this duplicate scan. If two such sessions appear on one day, review them directly instead of assuming the automated check will resolve them.

Evidence added from a screenshot or conversation uses a separate matching step before it is saved. When it matches an existing activity, it can fill missing fields while preserving provider facts; that path should not be treated as a reason to create a second record first and clean it up later.

Removing the extra copy

After you choose, delete the candidate from AgentRunCoach. The deletion hides it from activity lists and training calculations but remains recoverable. It does not erase the source activity at Strava or another service.

Ask for the affected day or week review again after cleanup so the coaching summary uses the corrected history.

Ask your coach

  • “Check the last 30 days for duplicate activities.”

  • “Show me why these two runs were flagged as duplicates.”

  • “Delete the duplicate copy but keep the activity with the fuller data.”

Related

  • When an activity is missing — Check the source and connection, retry the import, or recover a missing activity from a screenshot or the facts you remember.
  • Deleting and restoring activities — Hide an incorrect activity from local history and training calculations, or restore it later without changing the original provider record.
  • Your day and week reviews — Compare planned training with completed activities for one day or a whole week without losing the status of individual sessions.

Last updated