venu 2 - less time until watchdog fires?

something which adds to the case, even if you don't need full history, but just last (or first) 4 hours, it's also problematic then because applying order on the Sensorhistory object does not work properly on all devices (crashing - forgot which devices were affected)  

@Anshul.ConnectIQ I saw later on that it's due to the fact that the historization is longer on the venu device (eg 2880 samples for heart rate). I can work around it by limiting the scope of the loop. The question raises though if you have the possibility of the longer history should you then also not be able to browse the full history of that  type within 1 watch dog cycle. I think you ought to be able.

peterdedecker just because the device has a higher storage doesn't warrant the need for a higher watchdog timeout, WD timer is related to the VM instruction execution and at the core of the CIQ, nonetheless I will try to bring up this argument with the team. It will most likely be rejected

data lover is an example app, I check complete history of historic heart rate.

Apparently the venu 2 has more storage for this type. Question is if there's more storage should there also not be a longer watchdog timeout?

Do you have a code sample and know what API you were using that could have triggered this?