Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Incident Detection after activity has already been stopped

jmto

I don't know what has changed, but last week after couple of Trail runs when I've already stopped the activity it triggers incident detection without apparent reason.

Don't remember the first one properly, but the second happened yesterday. Was running, go to the end. Pressed stopped. Walked a little and started taking a leak and then during that incident detection starts making noises. There was no impacts that would explain it being triggered. So I don't see any reason it should have triggered. 

And why it even triggers after the activity is stopped already? Wasn't it supposed to happen during activity?

Have others noticed this happening? 

  • 0

    , I've never heard of that happening before, very strange! May I have permission to reach out via email so we can further investigate? 

  • 0

    For me it sometimes triggered at the end of a sprint when I sat down heavily on a low wall and put my hand down on the surface I was sitting on.

    On the other hand it has triggered correctly for me twice.

  • 0 in reply to Garmin-Sierra

    Hi, thanks for you answer. Yes it's weird and thought if some one else has seen similar thing happening. Apparently not as at least no responses yet. And like I've had this version for a while and didn't see that happen before.

    I think I'll try to debug this first by my own, that do I still get it happen and maybe have somewhat better understanding what might be triggering it.

    So I'll take you on that offer if I still see it happening more and manage to figure something out. As a software developer I know it's kind of impossible to fix something if there's no method for reproducing the error.

    At least today after running nothing.. 

  • 0 in reply to nowster

    Yes. That has happened to me also, but that's understandable that at first you have quick sprint and then you are static and leaning on your knees. Can't remember was the activity still on or pause, probably still on.

    But these has been like nothing obvious that could explain false triggering. But need to keep eye on, was those two just some weird flukes or do I still get it happening.

  • 0 in reply to jmto

    , that sounds great. I appreciate you seeing if it's some how reproducible. Please tag me if you have an update so I don't accidentally miss it!

  • 0 in reply to Garmin-Sierra

     I think I have some ideas now that might help to reproduce it. It happened two times recently me.

    These two cases was:
    - Trail run, following course. Pressing stop before finishing the course. Then got course completed and after that Incident detection.
    - Snowshoeing, following course. Not sure did I press stop before completing the course, but got the course completed and incident was detected.

    And like Snowshoeing shouldn't even support it. I think it's something related to following course and the course completed triggering it. 

  • 0 in reply to jmto

    Thank you for the information! May I have permission to email you to gather a few more details? 

    FYI, Snowshoeing is a supported activity profile according to Setting Up Incident Detection on a Garmin Device.

  • 0 in reply to Garmin-Sierra

    Yes you can.

    Interesting. If I go to Snowshoeing with my 955, I get the notification that it's not supported. 

  • 0 in reply to jmto

    Thank you. 

    Very strange! I will see if Showshoe needs to be removed from that FAQ. Thank you for catching that!

Copyright © 1996-2025 Garmin Ltd. or its subsidiaries