title: Rails 5.1 ActiveJob on Puma development not performing specific enqueued job
body: <p>I'm running Rails 5.1.4 server (Puma v. 3.10.0 in single mode), but having an issue with a specific ActionJob that get's enqueued correctly but often never performed.</p>
  
  <p>I have a handful of jobs. All but 1 specific job always gets performed asynchronously like expected shortly after enqueuing them.</p>
  
  <p>First time after a server restart my specific job gets performed correctly after a new queueing. But after the first successful run, it will not get performed on following enqueuings.</p>
  
  <p>I'm queueing all jobs generally with <code>perform_later</code>.</p>
  
  <p>I've tested queuing the specific job using <code>rails console</code> as well. Whenever I queue it in the console, it gets performed instantly. Even in same session. Also tried with same arguments as used in the application when it's getting queued in the <code>rails server</code>, but in server it only gets queued. Never performed.</p>
  
  <p>I've checked the log files - there is nothing, no errors, no fatals, no warnings. It simply states <code>[ActiveJob] Enqueued FooBaaJob</code>, but never performs the job.</p>
  
  <p>If the job actually failed, it should at least still get to write out <code>[ActiveJob] [FooBaaJob] [id] Performing FooBaaJob</code> in the log, but it doesn't.
  And per <a href="https://github.com/rails/rails/blob/master/activejob/lib/active_job/logging.rb#L78" rel="nofollow noreferrer">https://github.com/rails/rails/blob/master/activejob/lib/active_job/logging.rb#L78</a> it should actually catch and log the exception if it was failing. Secondly it never fails to run in console, so that shouldn't be the case.</p>
  
  <p>Any ideas about where to look?</p>