Duplicate workouts
closed
R
Roman
Hey guys,
I have a specific issue, I'm not sure it's common but it still exists for me. When I'm doing indoor cycling workout with apps like Zwift or MyWhoosh, I have to start 2 workouts in parallel: 1 on my watch with heart rate measurements on, 2 in the cycling app connected to my bike and chest heart strap. I do this because after I finish my workout it gets exported to Strava and then gets saved into Apple Health with no heart rate info (known Strava problem). And at the same time I have a second workout written from my AW with full heart rate measurement.
Apple Health does not double the calories and minutes for these 2 workouts as it sees they were done exactly at the same time. But Bevel sees these 2 workouts as separate ones and doubles my Strain. Since you don't have an option to delete workouts inside Bevel, can you at least teach an app to see these duplicate workouts done at the same time as one?
I know I can hide sources in the settings but this does not solve it for me as I have other Strava workouts I don't want to exclude.
Screenshots attached
Amanda
Merged in a post:
Merge Co-Incident Workout Events
P
Peter Chambers
Apple HealthKit seems to do a good job of merging or handling multiple workout entries during the same period of time.
The current use case I have is tonal and Apple Watch separately creating workouts. Apple is able to merge these events and only saves the active energy/calories burned, workout efforts, and minutes based on the “higher prioritized source” in the HealthKit data sources list.
Bevel captures some benefits of this currently by importing the merged calorie count, but I’m getting bad cardio load data as Bevel currently reads these as sequential workouts rather than a single one.
Here is an output from the bevel ai:
You're spot on—Apple Health’s deduplication logic was actually working for your
Total Active Energy
summary, which is why that 1,547 kcal number stayed consistent. It effectively filtered the overlapping calorie data so your daily total didn't explode.The "double counting" was really happening in the workout-specific metrics that Bevel calculates independently:
*
Strain Score
: Bevel sees two separate sessions and stacks the cardiovascular stress of both, which is why your Strain was sitting so high earlier.*
Cardio Load
: Each workout object adds its own "impact" score. Two logs meant twice the load being added to your 7-day trend, pushing you into that Overtraining
status.Now that the Tonal duplicates are gone, your Strain (68%) and Cardio Load (32) are actually reflecting a single session's impact.
Even with the calories being accurate, that
2,000 kcal deficit
is still massive. Since you usually aim for a 900–1,200 range, you're currently doubling your intended gap. If you’re feeling wiped or your strength plateaus, you might want to close that hole with a bit more protein tonight.Amanda
Merged in a post:
Handle duplicate entry workouts
A
Amr Amin
Now with Garmin integration, Bevel sees my Garmin activities that are also in Apple Health as separate activities. Bevel should identify that these are duplicates of the same activity, and accordingly the body battery and strain scores shouldn’t double count.
J
Justin
Same! Duplicate workouts in Apple Health aren’t recognized as such.
I don’t agree with your solution. I think your algorithm should just recognize that 2 workouts are happening at the same time and average the two or something like that. I delete dupes in Apple health but I don’t think everyone will do that and your data becomes inaccurate if you reply on the user to delete dupes.
Amanda
marked this post as
closed
J
Justin
Amanda please consider re-opening this
Amanda
Thank you for the feedback, Roman. We recognize people use multiple apps/wearables to track workouts and that there is the potential for duplication. We have thought about auto-deleting one of them, but ultimately decided to let the user make the decision on which one they want to keep in Apple Health, to prevent any confusion in Bevel. How does this sound?
M
Marcos
Not sure if you picked a wrong example, but I se HR info on both screenshots, the one from zwift has the distance on top of that and from a better sensor.
Looks to be a non issue from where I can see.