My profile link : wilberfan - CityStrides
I’ve never seen this before. They both have identical mileage, but you can see that the 2nd entry has no progressed or completed streets.
Is it safe to delete the 2nd entry? 
I see that you have multiple services connected to CityStrides, but your account is private so I can’t view any more than you’ve shared here.
If you started tracking yourself with your Garmin device, and then also started tracking yourself with MapMyFitness or Runkeeper, and then saved both … That would result in the duplicate activities arriving in CityStrides, because I match on exact start times & in your case you would have two different start times.
If that’s the case, I would advise against doing that and instead set up a data synchronization flow where you track yourself in one place and then allow the data to sync automatically via the underlying services to other places.
Or, if you must do that for some reason, I’d advise you to pause the connection for one of those services you use.
If that’s not the case, I might need to take a closer look at the underlying data. If you share links to each activity, I can grab their IDs and look at things directly in the database.
Hey, James. I’ve de-privatized myself for now so you can look under the hood.
I haven’t changed the way I track an activity: just via the Garmin watch. As far as I know, it then syncs to the other services via Garmin. This is how I’ve been doing it for months.
Here are the two activities:
First the ‘real’ one: wilberfan's activity on August 18, 2024 - CityStrides
Then the duplicate: wilberfan's activity on August 18, 2024 - CityStrides
The start times are different:
Garmin => Sun, 18 Aug 2024 11:26:47.000000000 EDT -04:00
Runkeeper => Sun, 18 Aug 2024 11:26:52.000000000 EDT -04:00
(displaying in EDT because it’s auto-converted from the stored UTC for my database session)
You’re safe to delete wilberfan's activity on August 18, 2024 - CityStrides from the vertical three dot menu next to the activity’s date. You can also choose to ignore it.
Let’s see if this continues to happen or if it was a one-time glitch in the Garmin/Runkeeper connection.
1 Like