I experience many bugs with Incident Detection, but there is only 1 that I find to be truly unacceptable. About half the time after an Incident Detection alarm is triggered, I am unable to cancel it to stop the alarm sound and prevent a notification being sent to my emergency contact. The alarm sounds, but the screen of my Edge 530 does not indicate that an incident was detected. When this happens, I simply have to wait for the alarm sound to stop. Usually, my contact is notified, which is annoying for both of us, but sometimes my contact is not notified, which is even more concerning!
I see that these types of issues have been complained about for years. How has this issue not been fixed yet? I understand that false alarms are unavoidable, and there will be other bugs too, but, as a programmer of industrial automation systems, I know that is not that hard to ensure that an alarm is cancelable once triggered.
In case any of the following is relevant: I experience this problem primarily when using saved routes from the TrailForks app, using the mountain bike profile. My Edge 530 is less than 2 years old and has the latest update installed.