Support for re-enque later, or drop-previous

[Genkilabs]

Hello, I love this gem, thank you.
I have a use case where when a job is enqueued I'd like to keep pushing back the time of a scheduled job until it is executed without being re-requested.
ie.

• job is scheduled to run in 1 hour.
• before that job runs it is re-requested
• I'd like to either push it back to 1 hour from the new request, or, drop it and schedule a new one in 1 hour.

Perhaps I could do this with context to the job that was locking out the requested job?
unique :until_executed, on_conflict: ->(job, locked_job) { locked_job.drop(); job.enqueue(wait: 1.hour) }
or
unique :until_executed, on_conflict: ->(job, locked_job) { locked_job.reenque(wait: 1.hour) }

Any advice on how to best do this?

[akostadinov]

You can use on_conflict: :log. Then use the notification:

    ActiveSupport::Notifications.subscribe('conflict.active_job_uniqueness') do
|name, start, finish, id, payload|
      payload[:job].reenque(wait: 1.hour)
    end

[DanAndreasson]

This behavior really surprised me and was the cause of a nasty bug. I assumed that it would retry 5 times as usual.

Should the lock be released before the rescheduling occurs?

  unique :until_executed, lock_ttl: 10.minutes, on_conflict: :log
  retry_on CustomError,
           wait: :exponentially_longer,
           attempts: 5