Is the Watchdog Count documented somewhere for watch models ?

I found what I'm looking for, though collecting the info is time consuming.

In  AppData\Roaming\Garmin\ConnectIQ\Devices there is a folder for each device.

In each device folder there is a   simulator.json file.

At the bottom of that file there's an entry called "watchdogCount".

Given that so many of us have run into this issue, it's too bad that this information isn't clearly and directly available in the reference documentation so that we (I) don't have to spend my time hunting for it.

I loved the analogy made in a post about this... it's a speedlimit that you can't know until you're pulled over.

Far from ideal.

Not as important as understanding why the  watchdog is being triggered.  Your app executed too long without returning to the VM.  It catches things like infinite loops and prevents an app from hogging the processor.

Hi Jim,

I understand, but knowing which devices have the shortest watchdog Count allows useful testing. 

Not having that information means you may have a problem in the field that you don't know about until the app crashes on some user.

A while ago I wrote some scripts to parse the json files for the devices using php and postgresql so I could select what columns I wanted. Here's a list that isn't more than a month or two old, ordered by part number. I've found this to be useful for older devices, so I can break up some long calculations over two or three seconds that a newer device could do in one pass. Careful what you wish for.

Fantastic.

That's exactly the kind of thing that I was looking for.

I suspect others who happen across this will find it helpful too.

Thanks Andy

This is awesome!  What kinds of calculations do you need to do that are so long-running?  I may have some ideas how to help.

I’m reading and parsing enough data that the watchdog as being triggered. I’ve broken it up into a multi pass process but want to test against the worst case device to ensure that no user encounters a problem.