# Garmin FIT fields not coming in (Possible Garmin is Filtering Data prior to sending to intervals.icu)

**URL:** <https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287>\
**Category:** Bug Reports\
**Created:** [10 March 2026 09:30 UTC](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287 "2026-03-10T09:30:46Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![kvj](https://forum.intervals.icu/user_avatar/forum.intervals.icu/kvj/32/46392_2.png) [@kvj](https://forum.intervals.icu/u/kvj)\
**Post date:** [15 March 2026 14:49 UTC](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287/21 "2026-03-15T14:49:42Z")

</div>

> [@Nik\_Om\_Cinderella\_Ri](#):
>
> FIT Garmin API - The “Activity Metrics” row is gone. (This is where training effect is stored) - File Size 580kb

still there, for some reason

 ![grafik](https://forum.intervals.icu/uploads/default/original/3X/a/1/a11aa14561d057f3bda67a63f659191f29f4ea04.png)

---

<div class="post-metadata">

**Author:** ![pepe](https://forum.intervals.icu/user_avatar/forum.intervals.icu/pepe/32/36539_2.png) [@pepe](https://forum.intervals.icu/u/pepe)\
**Post date:** [15 March 2026 15:06 UTC](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287/22 "2026-03-15T15:06:10Z")

</div>

Fit file message number 79, 140 and 147 gone, and many message number 18,19 and 20 fields gone.

---

<div class="post-metadata">

**Author:** ![app4g](https://forum.intervals.icu/user_avatar/forum.intervals.icu/app4g/32/41800_2.png) [@app4g](https://forum.intervals.icu/u/app4g)\
**Post date:** [15 March 2026 15:09 UTC](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287/23 "2026-03-15T15:09:45Z")

</div>

assume 1 file saves 50kB  
The API sends out say, 1 million per day = 50MB  
Doesn’t seems like much savings

---

<div class="post-metadata">

**Author:** ![kvj](https://forum.intervals.icu/user_avatar/forum.intervals.icu/kvj/32/46392_2.png) [@kvj](https://forum.intervals.icu/u/kvj)\
**Post date:** [15 March 2026 16:19 UTC](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287/24 "2026-03-15T16:19:00Z")

</div>

I don’t think they’re doing it for the bandwidth saving reasons.

If Garmin intentionally removes those fields - they remove “their”, or proprietary calculated fields and leave access only to “your” data (HR, GPS, Pace, Power). Basically you get access only to what you’ve uploaded to Garmin.

---

<div class="post-metadata">

**Author:** ![jspira](https://forum.intervals.icu/user_avatar/forum.intervals.icu/jspira/32/47730_2.png) [@jspira](https://forum.intervals.icu/u/jspira)\
**Post date:** [15 March 2026 19:21 UTC](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287/25 "2026-03-15T19:21:52Z")

</div>

I agree. It seems more likely to be about directing user traffic than about saving bandwidth on responses to API calls. Users will go to Garmin Connect to the extent that it presents information that they can’t see anywhere else.

---

<div class="post-metadata">

**Author:** ![DarKen](https://forum.intervals.icu/user_avatar/forum.intervals.icu/darken/32/72559_2.png) [@DarKen](https://forum.intervals.icu/u/DarKen)\
**Post date:** [15 March 2026 21:42 UTC](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287/26 "2026-03-15T21:42:01Z")

</div>

That would be somewhat understandable if not for how limited connect is. Rounding, lack of custom charts and tables… A lot not within control of the user.

---

<div class="post-metadata">

**Author:** ![R2Tom](https://forum.intervals.icu/user_avatar/forum.intervals.icu/r2tom/32/50144_2.png) [@R2Tom](https://forum.intervals.icu/u/R2Tom)\
**Post date:** [16 March 2026 04:39 UTC](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287/27 "2026-03-16T04:39:34Z")

</div>

Well, maybe just the next step to “force” people into their subscription model

---

<div class="post-metadata">

**Author:** ![DarKen](https://forum.intervals.icu/user_avatar/forum.intervals.icu/darken/32/72559_2.png) [@DarKen](https://forum.intervals.icu/u/DarKen)\
**Post date:** [16 March 2026 12:20 UTC](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287/28 "2026-03-16T12:20:05Z")

</div>

It’s frustrating that the fields are still there if I export from Garmin Connect myself though…

---

<div class="post-metadata">

**Author:** ![MedTechCD](https://forum.intervals.icu/user_avatar/forum.intervals.icu/medtechcd/32/40383_2.png) [@MedTechCD](https://forum.intervals.icu/u/MedTechCD)\
**Post date:** [16 March 2026 12:32 UTC](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287/29 "2026-03-16T12:32:21Z")

</div>

I wonder if things are different for other platforms, like TP for example…

---

<div class="post-metadata">

**Author:** ![Andreas\_Schnederle-W](https://forum.intervals.icu/user_avatar/forum.intervals.icu/andreas_schnederle-w/32/37514_2.png) [@Andreas\_Schnederle-W](https://forum.intervals.icu/u/Andreas_Schnederle-W)\
**Post date:** [16 March 2026 12:37 UTC](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287/30 "2026-03-16T12:37:32Z")

</div>

> [@DarKen](#):
>
> It’s frustrating that the fields are still there if I export from Garmin Connect myself though…

wouldn’t phrase it like that … I would say: Thank god (Garmin?!?) that they are still there in the manual export …

---

<div class="post-metadata">

**Author:** ![pepe](https://forum.intervals.icu/user_avatar/forum.intervals.icu/pepe/32/36539_2.png) [@pepe](https://forum.intervals.icu/u/pepe)\
**Post date:** [16 March 2026 12:40 UTC](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287/31 "2026-03-16T12:40:14Z")

</div>

> quote  
> [mipapo][Discrepancies Between FIT Files from Garmin Connect and API (API Downgraded?) - Discussion - FIT SDK - Garmin Forums](https://forums.garmin.com/developer/fit-sdk/f/discussion/432872/discrepancies-between-fit-files-from-garmin-connect-and-api-api-downgraded/2018621)) in reply to [Hellkeeper](https://forums.garmin.com/developer/fit-sdk/f/discussion/432872/discrepancies-between-fit-files-from-garmin-connect-and-api-api-downgraded/2018354)

> "We got an answer by Garmin “All messages and fields previously documented in the FIT SDK are still available. Undocumented messages and fields are being removed before files are sent to third-party platforms. "  
> I hope DcRainmaker writes a blog post about it. (People: please ping him about it)”

---

<div class="post-metadata">

**Author:** ![DarKen](https://forum.intervals.icu/user_avatar/forum.intervals.icu/darken/32/72559_2.png) [@DarKen](https://forum.intervals.icu/u/DarKen)\
**Post date:** [16 March 2026 12:47 UTC](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287/32 "2026-03-16T12:47:19Z")

</div>

Uggghhhh yeah I guess but it’s created a chore I didn’t have a week ago…

---

<div class="post-metadata">

**Author:** ![pepe](https://forum.intervals.icu/user_avatar/forum.intervals.icu/pepe/32/36539_2.png) [@pepe](https://forum.intervals.icu/u/pepe)\
**Post date:** [17 March 2026 15:54 UTC](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287/33 "2026-03-17T15:54:19Z")

</div>

> [@kvj](#):
>
> If Garmin intentionally removes those fields - they remove “their”, or proprietary calculated fields and leave access only to “your” data (HR, GPS, Pace, Power). Basically you get access only to what you’ve uploaded to Garmin.

Just adding to this—message 147 is a clear example.

Garmin isn’t just removing proprietary fields. They’re stripping out user administered sensor settings like:

```
Sensor name

Crank length

Wheel size

Footpod Calibration factor

"Use for speed/distance" toggle

```

These aren’t Garmin-calculated metrics—they’re settings users configured to ensure accurate data. Without them, we lose critical context for interpreting power, torque, speed, and distance.

---

<div class="post-metadata">

**Author:** ![Laurent\_Caron](https://forum.intervals.icu/user_avatar/forum.intervals.icu/laurent_caron/32/37186_2.png) [@Laurent\_Caron](https://forum.intervals.icu/u/Laurent_Caron)\
**Post date:** [19 March 2026 00:32 UTC](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287/34 "2026-03-19T00:32:01Z")

</div>

Not sure if anything changed in the Garmin API, but I just came back from a run and I see a VO2max value populated now 👍

---

<div class="post-metadata">

**Author:** ![app4g](https://forum.intervals.icu/user_avatar/forum.intervals.icu/app4g/32/41800_2.png) [@app4g](https://forum.intervals.icu/u/app4g)\
**Post date:** [19 March 2026 00:51 UTC](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287/35 "2026-03-19T00:51:26Z")

</div>

VO2 max can be present in the FIT file or sent via the API

---

<div class="post-metadata">

**Author:** ![Laurent\_Caron](https://forum.intervals.icu/user_avatar/forum.intervals.icu/laurent_caron/32/37186_2.png) [@Laurent\_Caron](https://forum.intervals.icu/u/Laurent_Caron)\
**Post date:** [19 March 2026 01:14 UTC](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287/36 "2026-03-19T01:14:20Z")

</div>

Right, but I never download the fit files manually. I use automatic sync from Garmin to intervals.

Also, I had the same issue as reported above from March 10th to March 17th inclusive. No VO2max value for these dates. I run everyday, and today was the first day the VO2max value is back.

 ![Screenshot_20260318-211553](https://forum.intervals.icu/uploads/default/original/3X/3/6/36988f8ddbc22ba63021dd4372b9ab052d70a16c.png)

---

<div class="post-metadata">

**Author:** ![dcrainmaker](https://forum.intervals.icu/user_avatar/forum.intervals.icu/dcrainmaker/32/77041_2.png) [@dcrainmaker](https://forum.intervals.icu/u/dcrainmaker)\
**Post date:** [19 March 2026 10:05 UTC](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287/38 "2026-03-19T10:05:27Z")

</div>

The change was rolled back last night, while they take a deeper look at things.

Behind the scenes, I’m continueing to push that the original FIT file is what’s sent. Never a special variant of it. To me, it’s the cornerstone of what Garmin initially promised at decade+ ago when sync first started happening.

---

<div class="post-metadata">

**Author:** ![Andreas\_Schnederle-W](https://forum.intervals.icu/user_avatar/forum.intervals.icu/andreas_schnederle-w/32/37514_2.png) [@Andreas\_Schnederle-W](https://forum.intervals.icu/u/Andreas_Schnederle-W)\
**Post date:** [19 March 2026 10:27 UTC](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287/39 "2026-03-19T10:27:23Z")

</div>

Hey Ray,

It’s great to see you looking into this — thanks for the update, and welcome to the board! 😉

I really hope Garmin will continue to make all of the data available in the long term, since it’s the foundation of what has grown into a pretty large ecosystem by now.

Thanks again,  
best regards from Tyrol,  
Andreas

---

<div class="post-metadata">

**Author:** ![DarKen](https://forum.intervals.icu/user_avatar/forum.intervals.icu/darken/32/72559_2.png) [@DarKen](https://forum.intervals.icu/u/DarKen)\
**Post date:** [19 March 2026 16:25 UTC](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287/40 "2026-03-19T16:25:24Z")

</div>

To confirm coming the fields are coming through fine for me from my run at lunch time today.

Thanks to our new celebrity member for any advocating done on our behalf!

---

<div class="post-metadata">

**Author:** ![ArnaudL](https://forum.intervals.icu/user_avatar/forum.intervals.icu/arnaudl/32/60740_2.png) [@ArnaudL](https://forum.intervals.icu/u/ArnaudL)\
**Post date:** [24 March 2026 07:17 UTC](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287/41 "2026-03-24T07:17:33Z")

</div>

Hi.  
I was having the same issue yesterday.  
My rides are ok in Garmin, but here, I am missing a lot of dats.  
Generated the FIT file from Garmin and imported manually here, same.

I will have a look today after my ride if this is still ongoing

Any news on that matter?

[Previous page](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287.md?page=1)

[Next page](https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287.md?page=3)
