cron schedule does not run when cronNextEx is in the past
joestubbs opened this issue · comments
If an actor is registered with a cron schedule, but its cronNextEx value ends up being in the past, the actor's cron never executes. There might be multiple ways that the cronNextEx could wind up with a value in the past. One is if Abaco's cron prometheus scraper is not running for a period of time or if the corresponding controller (CronResource) is down, crashed or otherwise fails to run the cron. Finally, it might be possible to turn the cron off for a period of time and then turn it back on only after cronNextEx is in the past.
Regardless of how cronNextEx might come to be in the past, we should update Abaco so that the cron still executes.
Fixed in #109.