This Resque plugin sends a notification when a job fails

Resque plugin to specify uniq jobs with the same payload per queue

Gem para dar retry de forma otimizada nos jobs que falharam do Resque

resque-pagerduty provides a Resque failure backend that triggers a Pagerduty incident when an exception is raised by a job.

Adds persistence to Resque jobs, and retry properties

Process Manager For Resque

Adds live GUI queue/worker management to resque-pool

quickly and easily fork a pool of resque workers, saving memory (w/REE) and monitoring their uptime

Restrict max number of resque jobs.

Enable ActiveRecord query cache for Resque jobs

Resque Plugin adding simple queue statuses.

A Resque plugin which allows you to create dedicated queues for jobs that use rate limited apis. These queues will pause when one of the jobs hits a rate limit, and unpause after a suitable time period. The rate_limited_queue can be used directly, and just requires catching the rate limit exception and pausing the queue. There are also additional queues provided that already include the pause/rety logic for twitter, angelist and evernote; these allow you to support rate limited apis with minimal changes.

The plugin is designed for sequential running of different jobs in the same queue across multiple queues. Specifically meant for running a variety of long-running background tasks scheduled ahead of time using something like reque-scheduler. May not be suitable for large scale operations.

Allowing Resque to handle queues accross multiple Redis instances

Make your custom reports to CSV in background using Resque with simple DSL

Usually Resque workers work on queues in the given order (if there is something in the first, work it, otherwise if the there is something in the second, work on it, and so on). This plugin randomizes the order of the queues based on weights, so that a given queue will be the first queue to try based on a probability weight. Given queues A, B, C, D and weights 4, 3, 2, 1, repsectively, A will be first 40% of the time, B 30%, C 20%, and D 10%. In addition, when B is first, A will be second 4/7ths of the time (4 / [4+2+1]), and so on. The project is inspired by resque-fairly, which unfortunately mathematically does not give you this control over the weights.

Ensures that only one Resque job with unique arguments is running at a time.

Declare resque queues serial and jobs in that queue will be run in serial mode

Integration of resque with resque-progress and resque-lock

Resque::Failure back-end which sends a Slack message whenever a Resque worker fails.