Have Watchdog timers changed "recently"

The Watch dog timer isn't based on time, but on number of bytecodes executed without returning to the VM.  It's also varied based on device for a long time.,

With a widget or glance on watches, there has always been a timeout of 2 minutes or less.  It's not the watchdog timer,  You need to interact with the app (tap, button press, etc) to restart the timeout.

Hi Jim,

I appreciate that. What seems to have happened over CIQ changes/SDK updates is that this timeout has changed eg VA4 was 2 minutes and now seems to be 90 seconds. Is this possible??

The va/venu timeout for glances/widgets has been shorter than the forerunner/fenix for a long time.  It's nothing new.  And something you don't see in the sim.  I just checked a venu2 and it looks to be 60 seconds.  I have a widget that tries to get data from a tempe sensor, and that can take a minute, so I've seen/heard about the shorter timeout on the va/venu devices for a long time,  I just tell the user to tap the screen every 30 seconds or so.  Same for things that try to get a GPS fix.  One of the first bugs I reported is the shorter timeout on the original va meant that it was even hard to do comm to get data after getting GPS.

Hi,

What confuses me is that these seem to have changed since my widget was first released. Used to work fine but now times out unless, as you  say, people flick through screens.

Thanks,

David

It's always varied by device,  Could it be you don't have many users where the timeout is on the low end?

Hard to tell as no stats on which devices have loaded the app. Just only now getting people coming out of the woodwork. 

If users are having issues, you can tell them to interact with your widget every 45 seconds or so, or make your widget/glance a device app so it never times out.  There is no way to extend this timeout on watches

Thanks Jim. All I know is that I'm getting too many issues raised so I am going to discontinue support for that app.