Skip to content
Aviv Levinsky edited this page Aug 13, 2018 · 2 revisions

Due to the simplicity of ActiveJob and the complexity of this gem there is no officially supported way of doing ActiveJob. If you want to use uniqueness you should be using Sidekiq directly. I know some projects started by using ActiveJob out of ignorance and someone has to do a whole lot of work to migrate the workers to use plain Sidekiq.

If you are in this position and you can't figure it out; I have done such migrations for really big clients before. I am a consultant with a ton of experience on such jobs. My rate is fair and I am easy to get along with.

If that is not an option I apologize. This gem won't support ActiveJob moving forward. It would require monkey patching too much.