Incident Detection too sensitive!

I have a Garmin Vivoactive 4S and this happened to me today after only turning the feature on this morning. I was cycling pretty gently on a bumpy road and then stopped, put my bike down and went to open a gate. By the time I was through the gate and looked to see why my watch was buzzing so much I saw it had texted all three of my emergency contacts and stopped my activity. I spent the remainder of my ride reassuring worried family members. I agree with others that there should be a pretty obvious blaring alarm if it’s about to send out an incident alert as I thought the watch was just buzzing to mark a lap or something. 

Happened to me today i had no idea until my fiance phoned to make sure i was ok but did you it stops tracking your route…. I lost 2 miles

I noticed this tread is 2 years old but I can't find any info if Garmin have sorted this issue.... as its happened to me today (x3 times on 2 years isn't bad but I didn't know until I had phone call from my family

The clapping thing has set off incident detection more than a few times for me. I start somewhat slow clapping to play with the dog and the alarm goes off. On the other end, I slipped on some ice and fell to the ground hard last week and nothing at all. I thought THAT was strange. 

Not in the same circumstances but, I was cycling and it kicked off without any justification, (it could've been a sudden change in my heart rate or I didn't get a reading for a small amount of time and that could've triggered it), I had to stop, twice, and cancelled it before sending messages and everyone going into panicking mode. It proves that it works, however it needs some improvements.

Regards,

Florin 

Do i remember right that were changes to the incident detection during one of the last sw-releases?

Terrible: today i had two false alerts.

First one - walking program. At one point i decided to run a few meters during that program. Just a few seconds after starting the run the countdown startet.
Second one (during that same walking activity) - i just stopped to have a look on my smartphone. A few seconds later the countdown began to start...

Ditto. On a road ride, just riding along, and I get a call from my wife asking what happened. Nothing happened. Even worse it stopped recording my ride and started a new one. for the incident.

So, I've had certainly more than a dozen FALSE INCIDENT DETECTIONS on my Garmin EDGE 830 and Garmin FENIX 6S Sapphire. The EDGE 830 is over 3 years old, the FENIX 6S is about 1-1/2 years old. 
I've had possibly TWO ACTUAL INCIDENTS DETECTED in all that time, both on the EDGE 830, while mountain biking, and they were only "ACTUAL" INCIDENTS because they involved very minor "crashes" that were really more like laying down the bike after riding over a log. Not really a crash, but a minor spill/step-out as I laid the bike down. OK, I get that it triggered the "INCIDENT DETECTION." 

But ALL of the other "DETECTIONS" were BOGUS. Some so totally ridiculous that I'd be ashamed of the product if I sold it. And these have RUINED the record of my rides a few times because no matter HOW HARD I tried to CANCEL THE NOTIFICATION AND THE INCIDENT, I could NOT STOP IT. The EDGE screen had the CANCEL option showing but it would not respond to my press no matter how I tried. 

THEN, when the INCIDENT gets reported, my wife has to follow up and see what's wrong. I have to stop and take the call and explain. Then LATER, I realize that the STUPID DESIGN by GARMIN is to END THE RIDE AT THE INCIDENT! HOW DUMB IS THIS!?? 

It was NOT an incident. I could NOT cancel it. I WANT MY RIDE RECORDED, WITHOUT GAPS or lost data. NO. It's CANCELLED. It has to be RESTARTED. And if I'm distracted with answering my wife's call, assuring all is okay, and then get back to riding without realizing the stupid device has stopped logging the ride, I have MORE fun... I have to STOP the "INCIDENT DETECTION" RECORD" and Restart a RIDE recording. 

And as it happened TODAY, with my FENIX 6S deciding that I had an incident WHILE I WAS STOPPED, adding some layers of clothes for a long descent on the bike, I pressed the button to CANCEL multiple times, held it, tried anything I could think of to stop it, IN VAIN. 

Message sent, wife called me, worked through that, then my bluetooth earpiece started going off, with the loud alert sound! WHAT??? This is AFTER the whole mess of trying to cancel, taking the call from home, now a nonstop racket that I could NOT SILENCE! The only thing on the phone was a notification that I could pull down and select, which opened to the notification screen, but NOTHING COULD BE DONE WITH THAT! Nothing could be pressed to cancel, nothing responded to touch anywhere. It just stayed as a notification in the top bar if I hit my back button, but it still was sounding off on my earpiece. 

I finally turned Bluetooth OFF TOTALLY, hoping that would stop it, but then the PHONE went nuts with the sound! I tried to use the app drawer to totally CLOSE DOWN Garmin Connect. Nope. Phone still sounding off. 

I had to REBOOT MY PHONE COMPLETELY and restart needed apps, like my VARIA RADAR app, and then proceed on the ride. And then 2 miles plus down the road, I realized the FENIX was now recording a "WORKOUT" called INCIDENT DETECTION. Unbelievable. I stopped that "activity" and Started recording another ride, just to make sure something was available for backup in case my EDGE 830 had issues later in the ride. I was using both, thankfully, so I didn't lose me ride today. This whole mess cost me many minutes of time dealing with it, standing around in the cold when I should be staying in motion and getting back before dark....

I DESPISE the INCIDENT DETECTION FEATURE and have totally shut it OFF yet again (my FENIX 6S is a recent warranty replacement, and apparently I hadn't deactivated that setting yet.) 

GARMIN, your execution of this feature is PATHETIC. It's bad enough that it is triggered far too easily, but the fact that these devices FAIL TO RESPOND TO THE CANCEL COMMAND on a FREQUENT BASIS is inexcusable. You totally destroy your own reputation because you fail to make these "features" function properly.

I'm way past believing you care...

I have a Fenix 7x Sapphire Solar. I had JUST finished (with no remarkable or sudden movements or anything like that) an important 22k trail run when I glanced at my watch to save the run to see it had already activated the emergency calls to the various members of my family (various in case one or two are busy or its early morning) and all hell breaks loose that Dad's half dead on a remote trail somewhere. I soon texted to let them know I was ok - but not after some very severe angst on their part. From my personal and selfish reasons the watch had stopped and Saved my run - had this been in the middle of the run I would have been very annoyed.  So, even with the latest generation watches this is still happening. Great innovation - poor and potentially dangerous execution. What if I had not seen it it go off in the middle of my bush run and they send out the search parties and helicopters etc!? Garmin - what do I do now? recalibrate or? ...