rails-activejob

I'm playing with Rails 4.2 app which uses ActiveJob backed by resque/sidekiq for email scheduling. When a user creates newsletter campaign a new job is created and scheduled on certain date. That's all great but what happens when the user changes the delivery date. In this case every job could check if it should be delivered or not thus invalid jobs would be ignored and only the last one would be executed. This could work but if a user would make 1k edits that would push 1k-1 invalid jobs into queue - not good. I believe that the existing job should be updated or replaced with a new one. As

I'm working on a reset_password method in a Rails API app. When this endpoint is hit, an ActiveJob is queued that will fire off a request to Mandrill (our transactional email client). I'm currently trying to write the tests to ensure that that the ActiveJob is queued correctly when the controller endpoint is hit. def reset_password @user = User.find_by(email: params[:user][:email]) @user.send_reset_password_instructions end The send_reset_password_instructions creates some url's etc before creating the ActiveJob which's code is below: class SendEmailJob < ActiveJob::Base queue_as :default def

This is my first processing jobs asynchronously I am implementing Sidekiq for background processing in my app. I will use it for reminder emails and in-app notifications. I am confused as to whether I should use Active Job to create a job that sends an email or a Sidekiq Worker to send an email. They seem to do the same thing and Rails 4.2 Active Job seems very new…is it replacing the need for a Sidekiq Worker? Below is the same sending a mailer code using an Active Job job and a Sidekiq Worker. I am using Whenever gem for scheduling. my_mailers.rb class MyMailers < ActionMailer::Base def some

Is there a way I can see how many (maybe even inspect each job?) jobs are there remaining in the queue? After some digging into source code here is what I found out: ActiveJob::QueueAdapters::AsyncAdapter uses a Concurrent Ruby thread pool to schedule and execute jobs. When you initialize the adapter in your configuration, you pass executor options , which in turn happen to be arguments to initialize method of Concurrent::ThreadPoolExecutor class. Created instance of Concurrent::ThreadPoolExecutor class has such methods, as: queue_length - The number of tasks in the queue awaiting execution.

Any idea how to get the Delayed::Job id from the ActiveJob enqueuing? When I enqueue a job I get back an instance of ActiveJob::Base with a @job_id , but that job id seems to be internal to ActiveJob. My best guess so far is just to walk down the most recently created jobs: active_job_id = GenerateReportJob.perform_later(self.id).job_id delayed_job = Delayed::Job.order(id: :desc).limit(5).detect do |job| YAML.load(job.handler).job_data['job_id'] == active_job_id end but that seems all kinds of hacky. Kind of surprised ActiveJob isn't returning the ID from Delayed::Job , especially since that