The Deep Dive Fix Files: Week Ending 6 June 2026

This is a weekly roundup of significant sports tech problems that the endurance community has encountered and, where possible, resolved. Each entry covers the issue, the affected hardware or software, and the current best fix or workaround known to the community.

---

Garmin Strength Training Auto Rep Counting Wrong, Exercises Misidentified and Weights Overwritten

Garmin’s strength training auto rep counter has been unreliable since the feature launched, and years of forum reports have not produced a fix. A survey conducted in April 2026 confirmed no progressive overload memory, Training Load that gives strength sessions less credit than runs of the same duration, and no per-muscle recovery modelling. The counter miscounts on exercises with less distinct wrist movement and routinely fails to register set boundaries correctly.

Exercise identification is wrong more often than it is right. Shoulder press reads as bench press, shrugs as squats, weighted back squats default to the bodyweight variant. The watch can detect only one exercise type per set and accuracy drops further when movements change within a session. The weight logging fault compounds the detection problem: entering a weight on the watch during a session does not guarantee it is preserved. When the activity is edited in Garmin Connect afterwards, the app silently overwrites manually entered load data with Body if it has misidentified the exercise as a bodyweight movement. A session with correctly entered loads can come out of editing showing bodyweight throughout.

Structured strength workouts carry a separate fault. Rep targets assigned in the workout plan are not recorded against the completed activity. The saved session shows no rep data unless the user edits it in Connect afterwards, which makes structured strength workouts useless for progressive overload tracking.

The community has settled on using the watch for what works: the set timer and the rest period countdown. Reps, weights, and exercise names are logged in a dedicated application such as Strong or Hevy. The watch data is ignored for everything else. This is the context in which Garmin is currently marketing Connect+ partly on Live Activity real-time rep display and a forthcoming Muscle Battery recovery metric. These are subscription features built on top of auto-detection the community does not trust. WHOOP’s competing MSK feature, released in February 2026, was validated across more than 10,000 repetitions with 97 percent repeatability.

---

Garmin Pool Swim Tracking Logging Wrong Distance, Extra Laps and Incorrect Stroke Counts

Garmin pool swim sessions are regularly recording badly wrong distances, with the watch adding phantom laps mid-length rather than at turns. The pattern is almost always over-counting: 700 metres swum recorded as 1100 metres, 3000 metres recorded as 3350. SWOLF scores are wrong downstream because they are calculated from stroke count per length.

The root cause is the turn and stroke detection algorithm, which runs on the wrist accelerometer and relies on a distinct motion signature at each wall touch: a firm push-off, a brief glide, and the first stroke beginning with the watch arm. Anything that disrupts that pattern, a slow push-off, a long passive glide before the first pull, an uneven pause mid-stroke, or a pace change within a length, can register as a turn that did not happen or miss one that did. Breaststroke and butterfly are more vulnerable than freestyle because the wrist signature at the turn is less distinct from normal stroke movement.

The technique adjustments that reduce miscounting: push firmly off the wall, begin a one to two second glide with a kick, and take the first arm stroke with the watch arm. Keep pace consistent within each length and avoid slowing into the wall in a way that the accelerometer reads as a stop. For interval sets, the lap button is more reliable than the pause button for marking rest periods, since the pause button can confuse the length counter on some firmware versions.

Verify the pool length setting before every session. A mismatch between the configured length and the actual pool is the first thing to check when total distance is wrong, and the setting carries over from previous sessions at different venues without prompting. For sessions already saved with wrong data, Garmin Connect allows editing of split lengths and merging incorrectly counted lengths under Activity Detail. This restores accurate SWOLF and pace data after the fact.

---

Garmin Live Track Failing on Race Day: The Link Expiry, the Contact Fault and the Frozen Position Fix

Garmin Live Track has four distinct failure modes, each needing a different fix. The same issues have been documented across multiple firmware generations and persist into current Garmin Connect builds. The Fenix 8 series added automatic per-activity Live Track triggering in April 2026 beta 22.23, which required an immediate bug fix in beta 22.24.

The most common fault is the LiveTrack Failed error at the start of an activity. In the majority of cases the cause is a Garmin Connect update that moved contact storage to the Garmin cloud server, invalidating contacts saved under the old system. The fix: open Garmin Connect, go to Live Track settings, remove all saved contacts, disable Live Track entirely, save, then re-enable it and add contacts again from scratch. This resolves the failed start for most owners.

The second fault is the sharing link expiring before or during the event. Live Track links carry a 24-hour default expiry. For a marathon set up the morning before the race, an ultra that runs past midnight, or any event where the link is shared in advance, the window can close before the finish. Enable Extend Live Track in the Live Track settings before sharing the link. This extends the default 24-hour expiry and should be on by default for anyone using Live Track for races.

The third fault is followers receiving a working link but seeing location data unavailable or a frozen position. This is a Garmin Connect app cache issue on the follower’s device, not a device fault. Clearing the Garmin Connect app cache on the follower’s phone resolves it in most cases. The notification email from Garmin also frequently reaches the spam folder on Gmail and Outlook, so checking there before concluding Live Track failed entirely is worth doing on race morning.

For Fenix 8 Pro owners using LTE Live Track without a phone, reliability is lower than phone-relayed Live Track. LTE signal drops in areas of marginal coverage cut the tracking feed, and a soft reset with backup restore has temporarily resolved recurring failures for several owners. This remains an open issue on current firmware.

---

Garmin Incident Detection Firing False Emergency Alerts During Runs and Rides

Garmin incident detection sends emergency texts and GPS location to nominated contacts when it detects a crash. It fires on sudden deceleration followed by minimal movement, which maps closely to a real crash but also to a sprint finish, stopping to pat a dog at the end of a run, clipping out at traffic lights, or a rapid stop on a descent. The feature has no sensitivity adjustment. The algorithm is fixed, and the only control available is enabling or disabling it per activity type.

The trigger pattern in practical terms: the watch looks for a high-G event, a sudden drop in speed or a sharp impact, followed by a period of stillness. Stopping from 25 km/h to zero in a hurry satisfies this without hitting anything. Patting a dog immediately after stopping, or clapping someone through a finish line, applies a rapid wrist movement followed by sudden stillness that the accelerometer reads the same way as a fall. MTB activity mode has incident detection disabled by default because Garmin recognised that trail surfaces produce near-continuous false trigger conditions.

The critical detail most owners miss: there is a 15 to 30 second cancellation window on screen after the trigger fires. If the incident alert appears and the owner responds within that window, the message does not send. The screen can be easy to miss during a hard effort, and some configurations go straight to sending without a clearly visible pre-alert. Wearing headphones removes the audible warning unless the haptic feedback is strong enough to notice through the arm.

If the message has already sent, an I’m Okay follow-up can be sent to all emergency contacts from the controls widget: swipe down from the watch face, select Incident Detected, choose I’m Okay. Tell your contacts this option exists so an I’m Okay message after a false alert does not read as a second emergency.

The structural fix is the per-activity setting. Disabling incident detection for cycling activities with frequent sudden stops, urban commutes, MTB routes, or any route with known stop-start patterns, and retaining it for isolated trail runs or road rides where a genuine incident leaves the athlete without other means of summoning help, is the correct configuration for most owners. The Forerunner, Fenix, and Edge all allow independent settings per activity profile.

---

Garmin Open Water Swimming GPS Recording Wrong Distance or Drifting Badly During Triathlon Swims

Garmin open water GPS has one constraint that matters directly for triathlon distance accuracy. The watch records a GPS position only when the watch arm is above water during the stroke recovery phase, giving one usable sample per stroke cycle at best on freestyle. The result is that the GPS track cuts corners around buoys, typically under-counting on triangular courses by 5 to 15 percent, while GPS drift accumulates at the pre-start where auto-pause does not operate in open water mode and can add distance before the swim begins.

Two settings make a real difference and both should be confirmed before race day. Recording interval should be set to one second, not smart recording. Smart recording takes fewer samples and makes the sparse GPS problem worse in open water. GNSS system should be set to All Systems with multiband enabled if the device supports it. The Fenix 8, Forerunner 965, and Epix Gen 2 get more usable position fixes per arm recovery stroke and produce noticeably better tracks than single-band models on the same course.

Course shape matters more than most owners expect. A straight out-and-back of 1500 metres is manageable: the algorithm can interpolate between fixes with reasonable accuracy. A triangular or L-shaped triathlon course with buoys 100 to 300 metres apart, where the watch must capture each directional change, produces the largest errors. If the GPS does not catch a turn it draws a straight line through it, cutting the corner and understating the actual distance swum.

Waiting for a solid GPS lock before entering the water is essential. Most Garmin watches show a filled or green signal indicator when lock is established. Starting the activity before lock is achieved produces the worst tracks. In a crowded triathlon start area near open water, GPS lock can take two to three minutes longer than normal and the watch should be turned on at transition setup, not at the water entry.

For post-swim data correction, exporting the activity as a GPX file and reimporting it to Garmin Connect calculates distance from raw GPS coordinates rather than from the OWS algorithm. The reimported distance is often closer to the measured course length. This does not help with pace monitoring during the swim but produces a more accurate saved record.

---

Frequently Asked Questions

Why is my Garmin rep count wrong during strength training?

Garmin’s strength training auto rep detection uses wrist accelerometer data to count repetitions. It is most accurate on exercises with a very clear wrist movement signature, such as dumbbell curls, and least accurate on movements with subtle wrist action, such as back squats, deadlifts, or any exercise where the watch arm is pressed against the body. The algorithm is not user-adjustable. The community workaround is to use the watch only for set timing and rest intervals, and to log reps and weights in a dedicated strength tracking application.

Why does Garmin overwrite my weights with “Body” when I edit a strength session?

When a strength session is edited in Garmin Connect after the fact, the app re-evaluates exercise identification. If it reclassifies a weighted exercise as a bodyweight movement, it overwrites the manually entered load with Body. This happens because the exercise detection algorithm misidentified the movement during the recording. The weight data loss follows from the detection fault, not from an editing bug in isolation. Avoiding post-session edits to sets where the exercise was misidentified is the only way to preserve manually entered weights.

Is Garmin Connect Plus strength tracking reliable enough to replace a dedicated app?

Based on current community evidence, no. Auto rep detection is unreliable across most compound movements, there is no progressive overload memory, Training Load undervalues strength sessions relative to cardiovascular training, and structured strength workouts do not record rep data against the completed activity without manual editing. The feature set Connect+ is marketing, including Live Activity and the forthcoming Muscle Battery metric, is built on auto-detection the community does not trust for accurate data.

Why is my Garmin pool distance much higher than what I actually swam?

The most common cause is the watch incorrectly detecting wall turns mid-length and adding phantom laps. The turn detection algorithm uses the wrist accelerometer and is sensitive to disruptions in the normal push-off and stroke pattern, including pace changes mid-length, a slow push-off, or a long passive glide before the first arm pull. The result is over-counting rather than under-counting in most cases. Technique adjustments at the wall, particularly a firm push-off and beginning the first stroke with the watch arm, reduce false turn detections.

How do I stop Garmin adding extra laps in the pool?

Push firmly off the wall, begin a one to two second kick-driven glide, and take the first arm stroke with the watch arm. Keep pace consistent within each length. Use the lap button rather than the pause button to mark interval rest periods. Verify the pool length setting in the watch matches the actual pool before the session, as a mismatch carried over from a different venue produces systematic distance errors.

Why is my Garmin pool SWOLF score wrong?

SWOLF is calculated as the sum of the time in seconds and the stroke count for each length. When the watch miscounts strokes or misidentifies set boundaries, the stroke count component of SWOLF is wrong and the score does not reflect actual efficiency. Fixing the phantom lap issue by adjusting wall technique reduces the stroke count errors and produces more accurate SWOLF readings.

Why is Garmin Live Track showing LiveTrack Failed?

The most common cause is a Garmin Connect update that changed how emergency contacts are stored. Contacts saved under the old system no longer work with the new cloud-based contact management. The fix is to remove all contacts from the Live Track settings in Garmin Connect, disable Live Track, save, re-enable it, and add contacts again. This clears the stale reference and resolves the failed start error in most cases.

Why did my Garmin Live Track link stop working during a race or ultra?

Live Track sharing links have a 24-hour default expiry. For events that run past the expiry window, or for links shared in advance before the race day, the link becomes inactive before the activity ends. Enable the Extend Live Track option in the Live Track settings in Garmin Connect before generating and sharing the link. This extends the default expiry and should be enabled for any race use.

Why does my Garmin Live Track show location unavailable even though the link works?

This is a Garmin Connect app cache issue on the device the follower is using, not a fault with the watch or the link itself. Clearing the Garmin Connect app cache on the follower’s phone resolves it in most cases. The notification email sent by Garmin at the start of a Live Track session also frequently lands in the spam or junk folder on Gmail and Outlook, so checking there before concluding that tracking never started is the first step.

What triggers Garmin incident detection?

Garmin incident detection looks for a sudden high-G deceleration followed by a period of minimal movement. Genuine crashes satisfy this, but so do an abrupt stop at a traffic light, a fast sprint finish that ends suddenly, patting a dog immediately after stopping a run, or riding over rough terrain and stopping quickly. The algorithm has no sensitivity adjustment and cannot distinguish between these scenarios. The only user control is enabling or disabling the feature per activity profile.

How do I stop Garmin incident detection sending false alerts?

The most effective approach is to disable incident detection for activity profiles where false triggers are common, particularly urban cycling, MTB riding, and any route with frequent stop-start patterns, while retaining it for isolated trail running or road cycling. When a false trigger fires, a 15 to 30 second cancellation window appears on the watch screen. Responding within this window stops the emergency message from sending. If the message has already been sent, an I’m Okay status update can be sent to all contacts from the controls widget by swiping down from the watch face and selecting Incident Detected.

How do I turn off Garmin crash detection for cycling?

Open the activity settings for the relevant cycling profile on the watch. Navigate to Safety and Tracking, then Incident Detection, and set it to Off for that profile. This disables incident detection for cycling activities only while leaving it active for running or other profiles where it is retained. The Edge cycling computers have the same per-profile control under the same settings path.

Why is my Garmin open water swim distance wrong or too long?

Open water GPS distance errors on Garmin watches are caused by the sparse GPS sampling rate in water. The watch can only receive a GPS fix when the watch arm is above the surface during the stroke recovery, giving one position sample per stroke cycle at best. On a triangular or L-shaped triathlon course this sparse sampling means turns are missed and the track cuts corners, under-counting actual distance by 5 to 15 percent. GPS drift before the start can add phantom distance. Both issues are reduced by enabling one-second recording and All Systems plus multiband GNSS in the open water swimming activity settings.

What GPS settings should I use for open water swimming on Garmin?

Set recording interval to one second rather than smart recording, which takes fewer samples and amplifies the sparse GPS problem in open water. Set GNSS to All Systems with multiband enabled if the device supports it. The Fenix 8, Forerunner 965, and Epix Gen 2 all support multiband and produce noticeably more accurate open water tracks than single-band models at the same settings. Wait for a solid GPS lock, confirmed by a filled signal indicator, before starting the activity and entering the water.

Why does my Garmin GPS drift and add distance before I start swimming in open water?

Open water swimming mode does not use auto-pause in the same way that running mode does, because the watch cannot reliably distinguish between a stationary swimmer treading water and very slow movement. GPS noise that running mode would filter out when pace drops below a minimum threshold accumulates as distance in open water mode while the athlete stands at the start. Waiting for a solid GPS lock before starting the activity and entering the water immediately after starting, rather than standing in the water while the activity runs, reduces pre-swim distance accumulation.

Last Updated on 5 June 2026 by the5krunner