Scheduled Unique Jobs Not Being Enqueued

[lsimoneau]

Since updating Sidekiq to 2.12.1, unique jobs that I try to schedule 5 minutes in the future with:

JobClass.perform_in(5.minutes, args)

do wind up in the schedule, but then when five minutes rolls around they go away and are not enqueued or performed. It looks like there was a change to the way Sidekiq uses middleware for scheduled jobs (it now calls client middleware when scheduled jobs or retries are put on the queue).

Is it possible that the sidekiq-unique-jobs middleware is setting the payload hash key when the job is scheduled, and since the new Sidekiq version also calls client middleware when the scheduled job is then enqueued, it's not enqueued because the hash is already there?

[lsimoneau]

I've had a closer look, and that is indeed what's happening. I'll put together a fix and send you a pull request.

[disbelief]

This also appears to be happening to jobs that aren't unique, if the sidekiq-unique-jobs middleware is in the chain.

I only use sidekiq-unique-jobs for certain workers, but I've noticed that any scheduled worker disappears from the queue at the time scheduled without being performed.

[disbelief]

I knocked out a quick PR (#17) that seems to solve the problem for me.