The same code has been working smoothly for a few months in the past…
The function is invoked as the result of a runIn(15, …) command.
It’s interesting to note that the error pops up only when the function executing that code is run as the result of a runIn() invocation; when it’s run as the result of a (temperature change) event, it runs smoothly…
def now = new Date()
def runTime = new Date(now.getTime() + (the time from now in seconds goes here))
runOnce(runTime, "what you were launching to goes here")
OK, thanks.
Do you have an ETA for when runIn() will be stable again? Are we talking hours? Days? Weeks? Months?
I’m asking because several of my smartapps rely on runIn(), and I need to know whether I should modify them to use runOnce() instead or if I should just live with some deteriorated behavior in the least critical ones - which I couldn’t afford with the app managing thermostats…