Mikael Henriksson

@glennfu @amclaughlin-valetude I had a look into this. The problem only occurs when there isn't a lock for the specific item arguments anymore. This would for instance occur when the...

@sharq1 in your situation you already have a unique job in the one that is trying to delay itself. You would have to use some sidekiq magic or the replay...

@sharq1 then what about the following: > This is likely related to the fact that within the worker itself I added rescheduling mechanism... Basically the condition is, if the job...

## TTL (Time To Live) This is a Redis term! Since we are backed by a Redis database I figured it would be cool to spread some of that lingo....

The lock would expire after 30 seconds then and duplicates would be allowed. Since v7.0.1 there is automatic cleanup of orphaned locks so you shouldn't really have to worry about...

If all the sidekiq options are supported then nothing will have to be done for it to work. The problem with ActiveJob used to be the sidekiq middleware and customizing...

Thank you for sharing! I really appreciate the answer and then it makes way more sense why people are using it. Given the support of sidekiq options work on a...

@longnd since I don't know `ActiveJob` I can't fully help you here. The assumption is that it would work but if ActiveJob is passing it's global id to the arguments...

I am currently working on adding some transparency and rethinking logging which would also help. Not able to cut out as much time as I would like but I appreciate...

Thanks for the suggestion @Laykou. I'll see if I can whip together something for the v7 release.