jobs cleanup #14

New Issue

2025-12-29T00:21:14+01:00

adam commented

2025-12-29 00:21:14 +01:00

Originally created by @jalberto on GitHub (Apr 10, 2015).

When a job is removed from crontab.rb, it must be "marked" as disable or similar so it doesn't run next time

Originally created by @jalberto on GitHub (Apr 10, 2015). When a job is removed from crontab.rb, it must be "marked" as disable or similar so it doesn't run next time

adam added the enhancement label 2025-12-29 00:21:14 +01:00

adam commented

2025-12-29 00:21:16 +01:00

@plashchynski commented on GitHub (Apr 10, 2015):

Fair enough, we will implement it in the next release.

@plashchynski commented on GitHub (Apr 10, 2015): Fair enough, we will implement it in the next release.

adam commented

2025-12-29 00:21:16 +01:00

@jalberto commented on GitHub (Apr 10, 2015):

great news :)

Probably will be useful to add a flag to each job, so job can be disabled without removing, eg:

Crono.perform(MyWorker).every 1.week, on: :monday, at: '13:00', state: :disabled

with a sensible default to :active

Then on crono start (or on demand) every job marked to remove can be deleted

@jalberto commented on GitHub (Apr 10, 2015): great news :) Probably will be useful to add a flag to each job, so job can be disabled without removing, eg: ``` Crono.perform(MyWorker).every 1.week, on: :monday, at: '13:00', state: :disabled ``` with a sensible default to :active Then on crono start (or on demand) every job marked to remove can be deleted

adam commented

2025-12-29 00:21:16 +01:00

@carolyn-idi commented on GitHub (Dec 1, 2015):

I've looked through the documentation and can not find a way to kill this process. I ran bundle exec crono -d. Is there a way to kill this process? Any help would be greatly appreciated. Thanks!

@carolyn-idi commented on GitHub (Dec 1, 2015): I've looked through the documentation and can not find a way to kill this process. I ran `bundle exec crono -d`. Is there a way to kill this process? Any help would be greatly appreciated. Thanks!

adam commented

2025-12-29 00:21:17 +01:00

@plashchynski commented on GitHub (Jun 26, 2016):

@ceospfx you could kill the process using the kill command and pid file:

kill `cat tmp/pids/crono.pid`

@plashchynski commented on GitHub (Jun 26, 2016): @ceospfx you could kill the process using the `kill` command and pid file: ``` kill `cat tmp/pids/crono.pid` ```

adam commented

2025-12-29 00:21:17 +01:00

@arronmabrey commented on GitHub (May 1, 2018):

Until this feature is implemented the manual way to remove one of the old jobs that still shows up in the web ui. Just grab the name/title of the job and hop in a rails console and run:

Crono::CronoJob.where(job_id: "Perform MyImportantJob every 300 seconds").first.destroy

@arronmabrey commented on GitHub (May 1, 2018): Until this feature is implemented the manual way to remove one of the old jobs that still shows up in the web ui. Just grab the name/title of the job and hop in a rails console and run: ``` Crono::CronoJob.where(job_id: "Perform MyImportantJob every 300 seconds").first.destroy ```

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/crono#14