> What happens when your node is down when it was supposed to execute and then comes back up? If you want at-least-once scheduling you’d probably use a library

> What happens when your node is down when it was supposed to execute and then comes back up? If you want at-least-once scheduling you’d probably use a library that writes a last-completed time to your db. > What happens around timezone changes and leap years? For wall-time scheduling you’d need to handle it, yes. Why would a service be better than a library though? > What does this thing do if a run takes so long that the previous run is still going? I think we’d need either another db entry or simply prevent overlap directly in the library. > How do you get logs/notifications if it fails? Same way as other things in your app that fails I guess. Perhaps logging a critical event? If you’re talking about external health monitoring then yes, you’d need to have a separate service by definition, preferably with a completely different provider/host.