Permalink
Browse files

Clarify uniqueness args, expiration and payload

Close #13
Close #20
Close #22
Explain #26
  • Loading branch information...
1 parent 3a94d0f commit b77f6a5ab8843656a10912bcff3a17fd46a68b76 @mhenrixon committed Jan 27, 2014
Showing with 7 additions and 0 deletions.
  1. +7 −0 README.md
View
@@ -24,6 +24,13 @@ All that is required is that you specifically set the sidekiq option for *unique
sidekiq_options unique: true
```
+For jobs scheduled in the future it is possible to set for how long the job
+should be unique. The job will be unique for the number of seconds configured
+or until the job has been completed.
+
+*If you want the unique job to stick around even after it has been successfully
+processed then just set the unique_unlock_order to anything except `:before_yield` or `:after_yield` (`unique_unlock_order = :never`)
+
You can also control the expiration length of the uniqueness check. If you want to enforce uniqueness over a longer period than the default of 30 minutes then you can pass the number of seconds you want to use to the sidekiq options:
```ruby

0 comments on commit b77f6a5

Please sign in to comment.