starred/crono
1
0
Fork 0
mirror of https://github.com/plashchynski/crono.git synced 2026-01-14 14:23:27 +01:00
Code Issues 35 Packages Projects Releases 9 Wiki Activity

Restart crono issue #45

New Issue
Open
opened 2025-12-29 00:21:50 +01:00 by adam · 4 comments
adam commented 2025-12-29 00:21:50 +01:00
Owner
Copy Link

Originally created by @louislewatcn on GitHub (Aug 10, 2017).

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?

Originally created by @louislewatcn on GitHub (Aug 10, 2017). 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?
adam commented 2025-12-29 00:21:51 +01:00
Author
Owner
Copy Link

@marcindrozd commented on GitHub (Nov 8, 2017):

I have the same issue as above.

@marcindrozd commented on GitHub (Nov 8, 2017): I have the same issue as above.
adam commented 2025-12-29 00:21:51 +01:00
Author
Owner
Copy Link

@edwardmp commented on GitHub (Feb 2, 2018):

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

@edwardmp commented on GitHub (Feb 2, 2018): I encountered the same issue, which is definitely unwanted behavior.
adam commented 2025-12-29 00:21:52 +01:00
Author
Owner
Copy Link

@amolbudkhe commented on GitHub (Feb 3, 2021):

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

@amolbudkhe commented on GitHub (Feb 3, 2021): @plashchynski I am also facing the same issue. I have to stop the Crono and restart it to get the scheduled rake job executed.
adam commented 2025-12-29 00:21:53 +01:00
Author
Owner
Copy Link

@mediafinger commented on GitHub (Mar 30, 2022):

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

@mediafinger commented on GitHub (Mar 30, 2022): 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 in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
enhancement
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/crono#45
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?