Survivability of Delayed Scene event actions over Vera Restarts/Reboots

Does anyone know how Vera tracks the “future” component of Scene events

eg. Turn Light on, then AFTER 7 hours, Turn Light off

I’m wondering how Vera is keeping track that it needs to wait 7 hours before turning the light off, and whether a Vera restart (Reboot, Fault-detect, or “Save”) operation would impact the “Delayed” element of this scene.

In particular, if this is just kept as in-memory state, then a Reboot would definitely impact the “Delayed” component and lead to the type of issues reported a few times in this forum, like this posting:

http://forum.micasaverde.com/index.php?topic=2006.msg7681#msg7681

If it’s in-memory only, then the longer the “Delay” component of the scene, the more likely something will occur to restart Vera and then it’ll forget to do that bit.

Anyone know?

It’s serialized in the user_data in a json tag called PendingScenes

Just in case folks read back-threads, via search etc, closing the loop with the MCV’s revised behavior as described in this thread:

http://forum.micasaverde.com/index.php?topic=2000.msg8362#msg8362

you'll lose the 'after 7 hours' part because delayed timers aren't stored in the database. Rather the 'pending' part is stored in memory, and gets lost if there's a power failure, etc