Skip to content
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

Open
louislewatcn opened this issue Aug 10, 2017 · 4 comments
Open

Restart crono issue #63

louislewatcn opened this issue Aug 10, 2017 · 4 comments

Comments

@louislewatcn
Copy link

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?

@marcindrozd
Copy link

I have the same issue as above.

@edwardmp
Copy link

edwardmp commented Feb 2, 2018

I encountered the same issue, which is definitely unwanted behavior.

@amolbudkhe
Copy link

@plashchynski I am also facing the same issue.
I have to stop the Crono and restart it to get the scheduled rake job executed.

@mediafinger
Copy link
Contributor

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. 🤦

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants