Hi @Doppy -- there's nothing inherently wrong with using
setTimeout in the manner you've described, however it is not done simply because there is a better way to do it.
For example, you're setting the timer, and saving a reference in the db so if the app restarts, it is re-loaded. That is fine, you'd do something similar with
However, when you call
setTimeout, the function reference is held in memory and cannot be garbage collected if needed since at some arbitrary point in the future it will be called upon. I don't believe the same happens with cron but I may be mistaken.