Troubleshooting Sidekiq

See the Sidekiq admin through the web, via <your identity url>/sidekiq/.

Consider whether it’s okay to clear your entire Sidekiq queue. In development, this is usually fine, but in production you probably want to avoid it, or you may lose incoming data like member upserts or record actions.

Before you can clear any jobs

• If jobs are stuck as “Running”, you can’t access them via any of the queues (Enqueued, Retries, Scheduled, Dead).
• Stopping Sidekiq won’t help because it restarts immediately and your jobs go back to “Running”.
• So you need to stop the Sidekiq process altogether (via the Heroku dashboard or other).
• Use the Sidekiq web console to find the JID or identify the type of jobs you want to remove, and then check out the sample code below for how to remove them from the rails console.

Clearing one or more specific jobs by JID

Queue names are strings like critical. Leave blank for the default queue (Queue.new.each).

  Sidekiq::Queue.new('YOU_QUEUE_NAME').each do |job|
    job.delete if ['MY_JID_HERE', 'AND_ALSO_HERE'].include? job.jid
  end

Clearing jobs by type

Sidekiq::Queue.new.each do |job|
  job.delete if job.klass == 'UpdateMemberAreasWorker'
end