Skip to content

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

Open
@jdkealy

Description

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?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

      Participants

      @jdkealy

      Issue actions

        old jobs not re-initializing when not first initialized with resque loner · Issue #33 · resque/resque-loner