Hello,
I’m having an issue with the time shown for one of my completed activities. After importing it, the duration displayed is different from what I see in Strava and Garmin Connect.
I suspect this is caused by a mismatch between total time, moving time, and elapsed time. During the activity, I manually paused the recording a few times during breaks.
Could this be a problem?
It also seems that the training load might not have been calculated correctly, because the system likely assumes the total duration equals the time spent under load, which is not accurate in this case.
Thanks in advance for your help!
Hi, could someone clarify whether this is a bug or expected behavior?**
I still don’t understand why the time shown here is different from what I see for the same activity on Strava or in Garmin Connect.
Also, can I rely on the calculated training load being accurate and properly reflected in my future training sessions?
Or should I manually adjust the activity to match the actual duration in order to ensure correct load calculation?
Strava:
Athletica:
Hi @Lurk … WRT load, I would consider checking your threshold settings. Your bike HR is set quite low relative to your other modes, and this might have affected the load calculations.
@Prof Thanks for your response regarding the threshold …
However, the main issue is that during the activity I paused the recording a few times (e.g. during breaks).
Other platforms like Garmin or Strava handle this correctly and show the actual moving time.
Athletica, on the other hand, doesn’t seem to account for these pauses properly — it shows a longer moving time than it should, and as a result, the training load is significantly overestimated.
Garmin vs Athletica:
strong text
Is this expected behavior?
And if so, should I manually edit the activity to reflect the correct duration and ensure accurate training load for future planning?