sidekiq-unique-jobs icon indicating copy to clipboard operation
sidekiq-unique-jobs copied to clipboard

Prevents duplicate Sidekiq jobs

Results 62 sidekiq-unique-jobs issues
Sort by recently updated
recently updated
newest added

**Describe the bug** We upgraded from 6.0.24 to 7.1.12 (alongside upgrade sidekiq from 6.1.2 to 6.4.0) Before the upgrade we were seeing ~300 reads/sec, and ~300 writes/sec After the upgrade...

**Describe the bug** I'm not sure if this is a bug or if I'm misunderstanding the documentation/usage of `:until_and_while_executing`. While `:until_and_while_executing` properly locks jobs which are queued but haven't started...

**Describe the bug** Jobs for workers that use `until_and_while_executing` sometimes get stuck because they appear to conflict with themselves. **Expected behavior** Executing `StatusRequestWorker.perform_async(123)` should run the job. **Current behavior** Note:...

**Describe the bug** I got `NoMethodError: undefined method `[]' for true:TrueClass` for every worker that has `until_and_while_executing` lock it happens when executing `perform_async` method **Expected behavior** perform_async should working fine...

Is there a way to run 1 job at a time no matter what are the job's arguments? **Here is the use case.** I'd like to create multiple invoices via...

**Describe the bug** I have some workers which are meant to run continuously. I'm using Heroku which restarts every 24 hours. I've noticed after the restart there will be locks...

The README says... > Starting in v5.1, Sidekiq can also fire a global callback when a job dies: In version 7, this is handled automatically for you. You don't need...

documentation
v7.x

**Describe the bug** The paragraph in the introduction describing conflict resolution stops mid-sentence: `By default, only one lock for a given hash can be acquired. What happens when a lock...

**Describe the bug** With the sidkiq options of: ```ruby sidekiq_options queue: :medium, retry: 3, lock: :until_executed, lock_expiration: 120 * 60 ``` When this worker has been run: ``` [1] pry(main)>...

**Describe the bug** It seems as though the after_unlock_callback is never called when using the until_and_while_executing callback. The callback works as expected when using :until_executed **Expected behavior** I expect the...