title: sidekiq retries exhausted with arguments
body: <p>I crawl <code>leads</code> from other sites and <em>activate</em> them at mine. With <code>Sidekiq</code> I run a  <code>HealthCheckerWorker</code> every hour to <em>deactivate</em> the lead on my site unless it's still up and running on the other site.</p>
  
  <p>Sometimes the <code>HealthCheckerWorker</code> throws an error, iE: <code>bad URI</code> etc... My dilemma here is that if the job fails 10 times, now in the Dead Job Queue, the <code>lead</code> is still considered <em>active</em> although it may be long gone on the other site.</p>
  
  <p>I thought the solution would be to add a <code>sidekiq_retries_exhausted</code> block like so:</p>
  
  <pre><code>sidekiq_retries_exhausted do |lead_id|
    Lead.find(lead_id).deactivate
  end
  </code></pre>
  
  <p>But as defined in the <a href="https://github.com/mperham/sidekiq/wiki/Error-Handling" rel="noreferrer">docs:</a></p>
  
  <blockquote>
    <p>The hook receives the queued message as an argument. This hook is called right before Sidekiq moves the job to the DJQ.</p>
  </blockquote>
  
  <p>So it only gets the <code>message</code> as an argument. How can I <em>deactivate</em> the lead after the retries are exhausted?</p>