-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restart crono issue #63
Comments
I have the same issue as above. |
I encountered the same issue, which is definitely unwanted behavior. |
@plashchynski I am also facing the same issue. |
This also happens with newly defined jobs - which I wanted to execute in the middle of the night, as they drain a lot of resources and which started running directly after deployment. 🤦 |
I have defined 2 jobs in cronotab:
Crono.perform(CheckBuildsAndNotifyJob, "Check Build Version", "AM").every 1.day, at: '09:30'
Crono.perform(CheckBuildsAndNotifyJob, "Check Build Version", "PM").every 1.day, at: '18:30'
The crono stopped yesterday for some reason and I restart my rails server as well as crono.
And the 2 jobs are triggered immediate I start crono.
It seems that it will memorize the unperformed jobs when crono is down and will run them on next start.
How can I disable this feature?
The text was updated successfully, but these errors were encountered: