Activity history problem on FR945 coming from edge 1040 after sync with GC mobile android

One issue here is that Edge 1040 is using training status 2.0 which 945 doesn't support. That means it calculates values a little differently and will sometimes or always show different training status.

Also remember to sync the Edge 1040 before each ride so it can download and calculate the new training load from the activities logged by 945.

This is a great page to use to look at all values related to training status and how it works: https://connect.garmin.com/modern/report/-1/all/last_four_weeks

Can you switch between the two devices and see how the values change? If both devices use the same version of training status and they are both synced before each ride you should see the exact same value for training load, but you can't do that since they use different versions.

I do have the same problem with edge 840 and FR945. This happened after I have installed the last update on edge 840. Since then I can’t go into activity details on FR945 and the historical data is displayed not correctly (eg vo2max, training status, etc.)

I did the same, re-paired, re-sync - nothing helped so far. To me looks like there is a problem with sync between devices.

Training status will be different between those two devices since they calculate it differently. 

VO2 max should be the same if you are looking at the same VO2 max value (there is one for cycling and one for all other activities). 

exact same issue since 20th March on my side. I cannot access the detailed activities recorded with Edge 1040 on my 945. Very weird ! I ve tried everything, maybe somehting to do with the recent edge 1040 firmware updates.....and training load too is screwed up on my 945 and will not piced the most recent one from Edge or GC...

Hi e7andy!

You say it right, but you don't answer the question that is asked.
Many of us know that the training status of the edge1040 differs from that of the FR945 and we are okay with it.
But as we have just explained to you, the problem is with the history transferred by the 1040 to the FR945 after synchronization, it always worked correctly before March 1, 2024.
The FR945 from the beginning always allowed the display and reading of the statistics of each outing carried out with the edge 1040, since the update of the 1040 and since March 1, the history is inaccessible in the FR945, there is just information of the activity carried out but no accessible value, it is blocked. There is a visual indication at the top right when you can open the history on FR945, after March 1, there is no longer this visual indication and pressing the button does nothing.
All activities prior to March 1 are accessible as before, as a result the FR945 can no longer even analyze the load and it tells us that we are in detraining.
The problem that you explain between the "training statuses" which differ between the 2 units, had no impact on the training history and load, and even on the training suggestions which were quite similar , sometimes the 945 indicated a different status than the 1040, but the charge was quite similar.
Now it's worse, everything is blocked and at zero, that is to say that as things currently stand, people who have an FR945 for their daily monitoring can no longer do so and Garmin has made the FR945 obsolete overnight after a simple 1040 update.

Same thing for me,  I have the 840 and 945.  The 840's activities can't be opened on the 945 and it shows my status as detraining.  Before this update the 945 would show approximately the same training status and at least allow me to open the activities to examine basic stats.   945 would suggest a fairly appropriate workout too.  Now its left in the dust.

Same issue here I believe. Activities seem to come over from my Edge 1040 Solar but I cannot “click into” the details any more as I once was able to do. It also appears that none of my training stats are coming over. Edge and GC on IoS display accurate training load and status while 945 shows training load of zero and Detraining status. Seems like the issue starting occuring in the last few weeks and post-GC beta install on my phone.