First activity with new Descent and I have it three times on GCW?

I did pair my watch with Garmin Dive and Garmin Connect App in my phone, which I think is the reason to this, but like, wtf still.

Hard to understand why there is these two programs and their relations and they give somewhat different data, so on?

Can someone explain or point to if this is explained somewhere? 

Should I just pair one of these or what?



Ps. Strava did detect them as duplicates and there's only one in Strava... 

  • Oh. Today it happened again, this time TWO.



    https://connect.garmin.com/modern/activity/14267783790 
    https://connect.garmin.com/modern/activity/14267783088 

    And yes, there was just one activity in the GARMIN\Activity.

    It seems that if it's bigger/longer activity this happens. Probably like the both apps trying to upload and checking when starting the upload is it there, but there's no deduplication check on the server or something?

    As like the first one was 875 KB => Three times, then two short runs without problems 96 KB and 100 KB. Then today Ski trip 847 KB => Two times.

    Oh well. probably like should contact Garmin support about this as software issues via local Garmin isn't the ideal way, but would be easier if some Garmin rep would take it from here. Do people know you are the regular Garmin persons in Descent forums? Maybe or  can help me here? 

  • Interesting, found that there's Settings -> Sync audit. Garmin Dive has empty sync audit. So all the syncs are from GCM.

    ---Username / User Displayname--- X / jmto ---GCM App Version--- 4.76 ---Timestamp--- Tue, Mar 5 2024 @ 8:01 PM ---Garmin Device Info--- [device information] unit id: 3461574137, product number: 4223, software version: 1562, device name: Descent Mk3i ---Android Device Info--- OS: Android Ver. Release: 14 Ver. SDK: 34 Ver. Codename: REL Locale: en_GB Manufacturer: asus Brand: asus Model: ASUS_AI2302 Device: ASUS_AI2302 Display: UKQ1.230917.001.34.1004.0204.88 release-keys Hardware: qcom Host: builder2021-RS720-E9-RS8-G ID: UKQ1.230917.001 Product: EU_AI2302 Radio: M2.6.16.35-VanGogh_000320,M2.6.16.35-VanGogh_000320 Serial: unknown Tags: release-keys Type: user User: builder2021 Board: kalama Bootloader: unknown Supported
    ABIs: arm64-v8a
    armeabi-v7a
    armeabi
    ---Sync Info--- ******************** SYNC STARTED: AUTOMATIC_PREFERRED ******************* ******************** SYNC RESULT: AUTOMATIC_PREFERRED: Descent Mk3i/38:F9:F5:3E:35:92 ******************** Overall Sync Status=FAILURE Overall Reason=NETWORK_UNAVAILABLE: No network available IsConnected=true GCUploadAgent=Uploadable=[FIT_TYPE_71, FIT_TYPE_70, FIT_TYPE_73, FIT_TYPE_72, GPSData, FIT_TYPE_52, FIT_TYPE_74, KPI, FIT_TYPE_32, FIT_TYPE_35, FIT_TYPE_57, FIT_TYPE_58, FIT_TYPE_38, FIT_TYPE_9, FitnessHistory, IQErrorReports, GOLF_SCORECARD, BACKUP_SUPPLEMENTARY, FIT_TYPE_61, ErrorShutdownReports, FIT_TYPE_41, FIT_TYPE_44, FIT_TYPE_66, FIT_TYPE_68, BACKUP_PRIMARY, FIT_TYPE_28, FIT_TYPE_49, FIT_TYPE_4, BLELogs, ULFLogs, WELLNESS_TYPE_1] Total Files=2: VisibleFailures=2 UPLOAD: ACTIVITY(4)/896239B - NETWORK_UNAVAILABLE: No network available - 404a11ee-0000-00e1-0100-0000000dacef UPLOAD: BIOMETRIC(44)/1030B - NETWORK_UNAVAILABLE: Previous network/GC unavailable failure - 404a11f2-0000-00de-0100-000000000406 *****************************************************
    
    ---Username / User Displayname--- X / jmto ---GCM App Version--- 4.76 ---Timestamp--- Tue, Mar 5 2024 @ 8:09 PM ---Garmin Device Info--- [device information] unit id: 3461574137, product number: 4223, software version: 1562, device name: Descent Mk3i ---Android Device Info--- OS: Android Ver. Release: 14 Ver. SDK: 34 Ver. Codename: REL Locale: en_GB Manufacturer: asus Brand: asus Model: ASUS_AI2302 Device: ASUS_AI2302 Display: UKQ1.230917.001.34.1004.0204.88 release-keys Hardware: qcom Host: builder2021-RS720-E9-RS8-G ID: UKQ1.230917.001 Product: EU_AI2302 Radio: M2.6.16.35-VanGogh_000320,M2.6.16.35-VanGogh_000320 Serial: unknown Tags: release-keys Type: user User: builder2021 Board: kalama Bootloader: unknown Supported
    ABIs: arm64-v8a
    armeabi-v7a
    armeabi
    ---Sync Info--- ******************** SYNC STARTED: AUTOMATIC_PREFERRED ******************* ******************** SYNC RESULT: AUTOMATIC_PREFERRED: Descent Mk3i/38:F9:F5:3E:35:92 ******************** Overall Sync Status=FAILURE Overall Reason=NETWORK_UNAVAILABLE: No network available IsConnected=true GCUploadAgent=Uploadable=[FIT_TYPE_71, FIT_TYPE_70, FIT_TYPE_73, FIT_TYPE_72, GPSData, FIT_TYPE_52, FIT_TYPE_74, KPI, FIT_TYPE_32, FIT_TYPE_35, FIT_TYPE_57, FIT_TYPE_58, FIT_TYPE_38, FIT_TYPE_9, FitnessHistory, IQErrorReports, GOLF_SCORECARD, BACKUP_SUPPLEMENTARY, FIT_TYPE_61, ErrorShutdownReports, FIT_TYPE_41, FIT_TYPE_44, FIT_TYPE_66, FIT_TYPE_68, BACKUP_PRIMARY, FIT_TYPE_28, FIT_TYPE_49, FIT_TYPE_4, BLELogs, ULFLogs, WELLNESS_TYPE_1] Total Files=3: VisibleFailures=3 UPLOAD: ACTIVITY(4)/896239B - NETWORK_UNAVAILABLE: No network available - 404a11ee-0000-00e1-0100-0000000dacef UPLOAD: BIOMETRIC(44)/1030B - NETWORK_UNAVAILABLE: Previous network/GC unavailable failure - 404a11f2-0000-00de-0100-000000000406 UPLOAD: FIT_TYPE_74/22167B - NETWORK_UNAVAILABLE: Previous network/GC unavailable failure - 404a1266-0000-00db-0100-000000005697 *****************************************************
    
    ---Username / User Displayname--- X / jmto ---GCM App Version--- 4.76 ---Timestamp--- Tue, Mar 5 2024 @ 8:31 PM ---Garmin Device Info--- [device information] unit id: 3461574137, product number: 4223, software version: 1562, device name: Descent Mk3i ---Android Device Info--- OS: Android Ver. Release: 14 Ver. SDK: 34 Ver. Codename: REL Locale: en_GB Manufacturer: asus Brand: asus Model: ASUS_AI2302 Device: ASUS_AI2302 Display: UKQ1.230917.001.34.1004.0204.88 release-keys Hardware: qcom Host: builder2021-RS720-E9-RS8-G ID: UKQ1.230917.001 Product: EU_AI2302 Radio: M2.6.16.35-VanGogh_000320,M2.6.16.35-VanGogh_000320 Serial: unknown Tags: release-keys Type: user User: builder2021 Board: kalama Bootloader: unknown Supported
    ABIs: arm64-v8a
    armeabi-v7a
    armeabi
    ---Sync Info--- ******************** SYNC STARTED: AUTOMATIC_PREFERRED ******************* ******************** SYNC RESULT: AUTOMATIC_PREFERRED: Descent Mk3i/38:F9:F5:3E:35:92 ******************** Overall Sync Status=SUCCESS IsConnected=true GCUploadAgent=Uploadable=[FIT_TYPE_71, FIT_TYPE_70, FIT_TYPE_73, FIT_TYPE_72, GPSData, FIT_TYPE_52, FIT_TYPE_74, KPI, FIT_TYPE_32, FIT_TYPE_35, FIT_TYPE_57, FIT_TYPE_58, FIT_TYPE_38, FIT_TYPE_9, FitnessHistory, IQErrorReports, GOLF_SCORECARD, BACKUP_SUPPLEMENTARY, FIT_TYPE_61, ErrorShutdownReports, FIT_TYPE_41, FIT_TYPE_44, FIT_TYPE_66, FIT_TYPE_68, BACKUP_PRIMARY, FIT_TYPE_28, FIT_TYPE_49, FIT_TYPE_4, BLELogs, ULFLogs, WELLNESS_TYPE_1] Total Files=3: VisibleFailures=0 UPLOAD: ACTIVITY(4)/896239B: ARCHIVED - 404a11ee-0000-00e1-0100-0000000dacef UPLOAD: BIOMETRIC(44)/1030B: ARCHIVED - DESTINATION_FAILED: File 404a11f2-0000-00de-0100-000000000406 was accepted but previously uploaded 409 to https://connectapi.garmin.com/upload-service/upload/metrics - 404a11f2-0000-00de-0100-000000000406 UPLOAD: FIT_TYPE_74/22167B: ARCHIVED - 404a1266-0000-00db-0100-000000005697 *****************************************************
    
    ---Username / User Displayname--- X / jmto ---GCM App Version--- 4.76 ---Timestamp--- Tue, Mar 5 2024 @ 8:32 PM ---Garmin Device Info--- [device information] unit id: 3461574137, product number: 4223, software version: 1562, device name: Descent Mk3i ---Android Device Info--- OS: Android Ver. Release: 14 Ver. SDK: 34 Ver. Codename: REL Locale: en_GB Manufacturer: asus Brand: asus Model: ASUS_AI2302 Device: ASUS_AI2302 Display: UKQ1.230917.001.34.1004.0204.88 release-keys Hardware: qcom Host: builder2021-RS720-E9-RS8-G ID: UKQ1.230917.001 Product: EU_AI2302 Radio: M2.6.16.35-VanGogh_000320,M2.6.16.35-VanGogh_000320 Serial: unknown Tags: release-keys Type: user User: builder2021 Board: kalama Bootloader: unknown Supported
    ABIs: arm64-v8a
    armeabi-v7a
    armeabi
    ---Sync Info--- ******************** SYNC STARTED: AUTOMATIC_STANDARD ******************* ******************** SYNC RESULT: AUTOMATIC_STANDARD: Descent Mk3i/38:F9:F5:3E:35:92 ******************** Overall Sync Status=SUCCESS IsConnected=true GCUploadAgent=Uploadable=[FIT_TYPE_71, FIT_TYPE_70, FIT_TYPE_73, FIT_TYPE_72, GPSData, FIT_TYPE_52, FIT_TYPE_74, KPI, FIT_TYPE_32, FIT_TYPE_35, FIT_TYPE_57, FIT_TYPE_58, FIT_TYPE_38, FIT_TYPE_9, FitnessHistory, IQErrorReports, GOLF_SCORECARD, BACKUP_SUPPLEMENTARY, FIT_TYPE_61, ErrorShutdownReports, FIT_TYPE_41, FIT_TYPE_44, FIT_TYPE_66, FIT_TYPE_68, BACKUP_PRIMARY, FIT_TYPE_28, FIT_TYPE_49, FIT_TYPE_4, BLELogs, ULFLogs, WELLNESS_TYPE_1] Total Files=1: VisibleFailures=0 DOWNLOAD: TRUE_UP(39)/1183B: ACKED - ffffffff-ffff-ffff-0000-0013490d1dc4 *****************************************************
    But like, I don't come very smart from these...they look just A-ok. I don't keep data on, normally, I don't want too much notifications for the phone, so just keep the data off. There's just one upload in the GCM sync logs. Garmin Dive has no Sync logs visible, and I am no smarter how the triple/double happens.

  • I checked the JSON data of all three activities. They are almost identical, and they all come from the device (none from the HRM-Pro). There is only a few very minor differences. For example only the activity ID ...468 contains the Intensity Minutes data (and you can see it on the web page too). And then, the activities ...468 and ..153 have identical upload timestamps, while the ID ..682 was uploaded 1s later.

    Don't you, by hazard, have the watch paired with multiple devices? For example a phone and a tablet? Or did you sync it over the USB cable?

    I'd also recommend having a look into the folder //GARMIN/Debug/ on the watch and see whether there is a crashlog file. If so, open it with Notepad, and check whether the timestamp of the last crash does not correspond to the upload time of the activity.

    And if you use an Android phone, go to the Device Sync Audit (at the bottom of the Settings menu), and browse through the sync audits around the timestamp of the activities upload (2024-03-03T10:59), and watch for errors or warnings.

    However, this is really a case for the developers, so I recommend contacting the Support at https://support.garmin.com, and insisting in forwarding the case directly to the developer team, unless they are already aware of other similar incidents and can add you to the case.

  • ... another possibility - don't you use by hazard a phone with multiple instances of the GC app? Such as for example Work profiles, or similar?

  • I've only paired Descent to my phone (GCM, and Garmin Dive). But like, now I did connect it to PC that has express and Descent added to it to look at the GARMIN\Activity folder.

    Looked at the Debug folder. Not seeing any crashlog's and error files are empty or nothing useful. 

    Device sync I posted here, which to me looks just a-ok. 

    And no, I don't have profiles on my Android. So just one GCM and Dive.

  • Apparently can't see the sync log from that triple time.. can't go back to that.. 21:41 for that day is the latest 7242 event, then can go one back 7241 with same timestamp and then got one that looks weird doesn't have timestamp and can't go more to the history... So those aren't for some reason available, but those today's double seemed normal to my eyes.

  • As I wrote - reach out to the Support. I am afraid we cannot really help you here. Personally, it is the first time I hear about such case, and I am a resident user on Garmin's forums since years. However, the Support has a knowledgebase built with millions of their users, so there is a better chance they can help (or forward it to the developers)

  • Looked these two new.. JSON's and diff, ok, changed the desc/name/type to one. but then the differences:

    - lastUpdateDate - yeah, have changed the data
    - uploadedDate - 1s difference

    And only one has:

    - "moderateIntensityMinutes": 138,
    - "vigorousIntensityMinutes": 36,

    And really minor difference in averageMovingSpeed.. But like have no idea what does add these intensity minutes.
    So yeah, one doesn't come much smarter from there either.

  • Well, I'm still having hopes up that my tagging will help, as my experience dealing with the local Garmin support with software issues haven't been the best experience and they would just need to be a middle man and more broken communication etc.

    I think I've seen some multiple uploads issues in these years, but not very recently and can't remember were they somehow user error or not. Like those duplicates from watch and HRM.

    And it's over midnight, next priority is sleep.

  • In activity menu which you will see after activity stop, when you can save it, discard, when you scroll down you will see HR download option. Same you will have in already saved activity if this activity was made with HRM-Pro connected.

    IMG_0583.tiff