Execution limit - scheduling tasks instead

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

Interesting because I thought ST is against pausing apps as it’s supposed to be an event driven architecture and I suspect pause() is a blocking call which then adds to your execution limit.

runIn(), runOnce(), pause(msec) which one to use in this example

I’ll try and shed some light on this. runIn() schedules a new execution of this SmartApp, calling the method specified in the number of seconds specified. With values less than 60 seconds, YMMV. pause() simply suspends the current thread, for the number of milliseconds specified (not to exceed 15 seconds). pause() is unsupported and should not be used. It will be removed in a future release. I considered adding it to the documentation with a big warning to not use it - but decided against documenting it at all. Regarding the timeout you experienced - because any SmartThings code (SmartApps or Device Type Handlers) execute within the SmartThings ecosystem along with other SmartApps or Device Type Handlers, there must be limits in place to the resources they use, so they do not negativel…

The right way to handle it would be use runIn and daisy chain it with a state.counter to track how many times it’s run. It’s more overhead but you won’t run into the issues you’re facing with limits.