How do you tell a specific Delayed::Job to run in console?

Question

For some reason, Delayed::Job's has decided to queue up but not excecute anything even though I've restarted it several times, even kill -9'd it and restarted it. It won't run any jobs.

Can I , in /console, specify a specific job and tell it to work?

Ex:.. Delayed::Job.find(x).run

possible duplicate of [Manually Retry Job in Delayed_job](http://stackoverflow.com/questions/3312054/manually-retry-job-in-delayed-job) — smathy, Aug 02 '12 at 04:27

score 179 · Answer 1 · edited Oct 25 '18 at 03:55

179

You can also do it like this:

Delayed::Worker.new.run( Delayed::Job.find(x) )

edited Oct 25 '18 at 03:55

Joshua Pinter

45,245
23
243
245

answered Nov 22 '13 at 13:34

David Tuite

22,258
25
106
176

29

this is the best answer, it removes a job after it is done. Thanks – m4risU May 21 '14 at 07:59
13

Delayed::Worker.new.run(Delayed::Job.find(id)) – mrt Oct 16 '14 at 10:54
I agree with @mrt 's comment, you should make sure that you run the correct job – Jonny Aug 23 '16 at 15:16
If i want to run multiple delayed jobs of a specific queue then how can i do that? please help – Zia Qamar Sep 02 '16 at 05:17
The only thing this DOESN'T do is mark the row as locked. – phil Jan 25 '17 at 14:12
This is a useful method to use from automated tests like rspec. – Bret Weinraub Jan 15 '20 at 15:22
Worked perfectly. Thank you very much! – Ifelere Bolaji Jun 09 '20 at 18:47

score 136 · Accepted Answer · answered Aug 04 '11 at 20:08

136

answering how to run specific job from console:

Delayed::Job.find(x).invoke_job

but you must remember that it won't run any other things like destroying job that was done or so on. just running the job/task.

answered Aug 04 '11 at 20:08

schiza

1,900
1
15
18

4

Read carefully the answer's author note: _"it won't run any other things like destroying job that was done"_. I say so because I did not read it and I was getting crazy. Check the [@DavidTuite's answer](http://stackoverflow.com/a/20146200/316700) – fguillen Nov 01 '16 at 07:25

score 0 · Answer 3 · answered Mar 20 '18 at 08:49

0

On Heroku I had a "stuck" job and just had to run heroku restart for the worker/job to start again.

answered Mar 20 '18 at 08:49

rassom

2,896
5
34
45

1

Thanks for the positive comment ;-) It could be that the person asking - or people coming to this question - had the problem on Heroku. – rassom Jan 16 '20 at 17:28

How do you tell a specific Delayed::Job to run in console?

3 Answers3

Linked