Selwin Ong

Yes, please open a PR for this. We should make an exception for `StartedJobRegistry` though, I don't think we should allow users to requeue jobs from there.

May I know your use case? You shouldn't enqueue the same job multiple times as that would lead to unexpected behaviors, like they'd store the result in the same Redis...

RQ works on the assumption that a job ID is unique, andd this leads to an optimization made in [this PR](https://github.com/rq/rq/pull/486). This optimization may improve the performance of removing a...

So I've been thinking about this a lot. [rq-scheduler](https://github.com/rq/rq-scheduler) is my first crack at attempting job scheduling and it allows cron style job scheduling like enqueing a job every minute,...

My advise would be to have the resource manager create a new job everytime and saves the new Job ID. Whenever a job is canceled, the resource manager can then...

No one is working on this as far as I know. It would be nice to have this feature though. Django uses [watchman](https://github.com/facebook/watchman) to trigger reloads. I'd accept a PR...

Mind opening a PR for this?

Are you sure the queue and worker use the same Redis connection? I'm not aware of any bug in RQ that could lead to a worker not seeing jobs that...

@atainter are you able to nail down whether the job was actually ever in the queue (pushed to Redis list)? I’m just curious because a number of people are reporting...

In that case, let me work on a patch that increases debug logging around this area so we can try to nail down what happens the next time this happens...