while_executing jobs being dropped

[RobsonKing]

Describe the bug
I am trying to use while_executing like the example in the myapp

I queue multiple of these jobs from the console

MonitorWorker.perform_async
MonitorWorker.perform_async

I expect the second job to run after the first job has finished.
Am I reading the documentation wrong? Is this not how it is supposed to work?

Expected behavior
I expect them to run one at a time.

Current behavior
jobs are skipped with

2022-12-22T23:36:57.229Z pid=1 tid=ovspqt5hl class=MonitorWorker jid=528c5d2ff25cd2cb414348b6 uniquejobs=server while_executing=uniquejobs:58b7929b9a8065c042fdf26167eed18e:RUN INFO: Skipping job with id (528c5d2ff25cd2cb414348b6) because lock_digest: (uniquejobs:58b7929b9a8065c042fdf26167eed18e:RUN) already exists

Worker class

class MonitorWorker
  include Sidekiq::Worker
  sidekiq_options queue: 'default',lock: :while_executing,
  lock_timeout: 100,
  lock_ttl: nil,
  lock_limit: 1,
  on_conflict: :reschedule

  def perform(thing)
     Rails.logger.debug "Starting"
     sleep(1)
     Rails.logger.debug "awake"
  end
end

[mhenrixon]

That is how it is expected to work. You'd have to use a conflict strategy if you want to handle it.

There is no preventing both jobs from starting at the same time, only that they don't execute simultaneously.

[RobsonKing]

Thanks for the quick reply,

I will investigate more after the holidays.

So if I want to move jobs to the schedule queue (or just allow them to execute after one has finished), rather than skipping then I should try a custom on_conflict strategy?

[strika]

That is how it is expected to work. You'd have to use a conflict strategy if you want to handle it.

Is that really true? Note that @RobsonKing is using the "reschedule" strategy in the example. Shouldn't that cause both jobs to be executed?

[RobsonKing]

I figured out my problem. I was changing my on_conflict strategy but not reloading my rails console. As a result things behaved like :log when I thought it was set to :reschedule. 🤕