
                    For background-jobs, we pick up the best solutions provided by github life savers.
                    If google brings you here, you are so lucky! These life savers are angels, they have well solved your problems.
                    So do not waste time scrolling the original issue threads just to dig out solutions... 
                    Here you are, you are welcome. Then, go back to work!
                    

Good question - this has been a source of confusion for new users Retry - a 'retry' is a job which has failed and will be retried sometime in the future 

sidekiq What does the "Failed" count mean?

@birthdaycorp I'm sorry you are frustrated but this will happen with any new system you learn 

sidekiq How do you kill "busy" jobs ?

I have the same issue and solved it by using sth like
ExecStart=/home/deploy/.rvm/gems/ruby-2.3.3/wrappers/bundle exec sidekiq -e production -C config/sidekiq.yml
Note that I change bin to wrappers

sidekiq Systemd production

Another approach: Right now if someone wants to use sidekiq they must configure the number of threads they want to run on or use the default (25) 

sidekiq Better integration between Sidekiq thread count and Active Record pool size.

Still trying to turn off New Relic for Sidekiq::Web using this:
https://docs.newrelic.com/docs/agents/ruby-agent/api-guides/ignoring-specific-transactions#page-load-timing-rum
In the meantime

sidekiq Truncated response body using Sidekiq dashboard w/New Relic

Have you tried disabling the query cache? It may be the source of the leak dunno You can test this in rails console:

If that replicate the problem 

sidekiq Understanding a leak that happens only when running job via sidekiq worker

@knopa the DashboardContextExtensions was mistakenly named OwinDashboardContextExtensions (please see your screenshot) 

Hangfire IDashboardAuthorizationFilter with .Net Core

In other words do you need the post.dup or the copy.save(validate: false) before copying the attachment?

From what I've tried yes 