Bug: Stress level is not recorded during a paused activity ("Resume later")

Steps to reproduce:

  • Start an activity, e.g. cycling
  • Record the 1st part of a cycling activity
  • Pause the activity by choosing "Resume Later"

After this, the stress level in the "Stress" widget is not measured / recorded any more. Once I resume, finish and save the activity, my stress level tracking will be working fine again.

Possible workaround:

  • After selecting "Resume later", reboot the watch. Stress level is tracked again (but activity is still paused and ready to be resumed).

Typical usage scenario (or how I'm daily running into this issue):

I commute to work by bike. After arriving at work in the morning, I pause the activity and resume it when I leave in the evening. However, I'm concerned about my stress level and body battery drain during my work day. Btw, this was working fine on my FR935.

  • It also won't record sleep if you want to continue the next day, not really a bug, more a known inconvenience (in the Fenix series). But feel free to inform Garmin that's not optimal.

    That it does work after a reboot is interesting and showing its unessaray to don't do it. 

  • Same usage scenario, but this issue on my FR935 forced me to use my 520 while just broadcasting HR. Now with the 955, it also appears to pause respiration rate, showing "disabled" and that "wrist heart rate monitor is disabled," although it definitely is still recording heart rate.

    Interesting that it worked for you on the FR935. I also tried your reboot workaround - it does not work on the FR955.

  • if you are concerned about stress etc during work Save the activity then start a new one. 

  • I am currently doing that with the 955, but would prefer to be able to save it as one activity while recording metrics during the day. As the original poster had requested.

  • Then you've made your choice to try to do something that the watch does not do. Knowing that, you either need to change what you do or accept you can't have what you want.

  • The forums are meant to be constructive. I appreciate your addition to thread traffic which may aid in visibility.

    As documented in numerous threads, users currently only learn by experience and not through any provided documentation or notification, stress/respiration/sleep/etc. are not recorded when using the Resume Later function. This is documented in numerous threads. This could easily be explained in a webpage about Resume Later. Those features could simply show a note saying "not supported while activity in progress" instead of what I reported above for respiration or attempting to measure for 30 seconds, ending in "try again," as it does for stress while an activity is paused for later.

    I agree with  that this isn't a bug, but if OP was actually able to work around it by restarting, it is owed some further explanation.

  • Thanks for your feedback!

    In the meantime (since a few weeks) the reboot workaround does not work for me anymore. But I occasionally experienced the watch to get stuck during boot (only observed when rebooting during a paused activity).

    I totally agree with you that this is indeed not a real bug, but also no intended design and could be an easy fix based on these facts:

    • No reasonable error message ("try again")
    • It used to work on the FR935
    • It used to work after reboot on the F7

    Even more interesting: my body battery drain (which is mainly based on stress level) seems to be tracked correctly even when the stress measurement does not work (stressful day->high drain and vice versa).

    To me, it totally looks like there is a background process which calculates stress level based on HRV data, which ist automatically paused when an activity is started but accidentally is not restarted when the activity is paused.

  • You are forgetting the sleep statistics not being recorded when an activity is paused.

  • Any chance this can be fixed any time soon ?

  • I do not think so. I just found out about this laat week but see that nothing was done about this user request for a long time.