Skip to content
This repository has been archived by the owner on Mar 23, 2023. It is now read-only.

Retry failed jobs #31

Open
maark85 opened this issue Apr 28, 2014 · 4 comments
Open

Retry failed jobs #31

maark85 opened this issue Apr 28, 2014 · 4 comments
Labels

Comments

@maark85
Copy link

maark85 commented Apr 28, 2014

Hello Kamisama.

In my resque-web i can retry jobs that are in Failed Queue.
It's possible to do the same thing on ResqueBoard? The Failed queue isn't displayed on Queues.

Thank you!

@wa0x6e
Copy link
Owner

wa0x6e commented Apr 29, 2014

It's not possible yet.

Unlike resque-web, Resqueboard is built to be also ran from another server than the one running the workers, so ResqueBoard does not always have access to resque.

It's in the to-do list though

@maark85
Copy link
Author

maark85 commented May 5, 2014

Ok. I've noticed that php-resque-ex writes in my Redis server in a different way.
When a job fail, he creates a key like that:

resque:failed:8f2cda7c57563bbee864f653fe026360

The php-resque sent the keys with failed to a default queue, and the worker automatically retried the job. It's possible to do that?

@wa0x6e
Copy link
Owner

wa0x6e commented May 9, 2014

I think it could be done, since the job's details are saved in the redis key.

But it should be implemented on php-resque-ex side, since it manipulates redis keys owned by resque, and not resqueboard.

@rubao
Copy link

rubao commented Jan 28, 2015

for retry jobs i'm using:

  • added a Resque_Event for onFailure for the Workers
<?php
Resque_Event::listen('onFailure', [callback]); 
  • in the callback I use ResqueScheduler to add the same job in 10min in the same queue
<?php
ResqueScheduler::enqueueIn(600, 'email', 'SendFollowUpEmail', $args);

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

No branches or pull requests

3 participants