Our Sidekiq redis instance is shared among multiple services.
So workers are available on one of the repo while not on the others.
When a scheduled or retried job is being consumed by the sidekiq poller running on another service, we need to to safely re-enqueue the task without exception.
Currently Sidekiq does re-enqueue jobs without the worker class without issue, but apparently the unique jobs middleware is not accounting for this case.
I have workaround the issue with a monkey patch, but an official fix is much appreciated. Thanks for the hard work!
Our Sidekiq redis instance is shared among multiple services.
So workers are available on one of the repo while not on the others.
When a scheduled or retried job is being consumed by the sidekiq poller running on another service, we need to to safely re-enqueue the task without exception.
Currently Sidekiq does re-enqueue jobs without the worker class without issue, but apparently the unique jobs middleware is not accounting for this case.
I have workaround the issue with a monkey patch, but an official fix is much appreciated. Thanks for the hard work!