old jobs not re-initializing when not first initialized with resque loner

[jdkealy]

Hi,

I have an issue with resque/resque-loner right now. I have a button to generate zips for around 400 files. When a site admin changes data about a photo, the event zip needs to be re-initiailzed.

For some reason, SOME jobs are being re-initialized however, when using resque loner, only some jobs don't get re-added to the queue and I'm wondering if perhaps I need to do something to my old jobs to get them to re-initialize (old as in before I started using resque loner)... Also are there some instances where resque does not show a pending job but resque loner has a job as pending, hence cannot re-enqueue the job?